I tried searching for research on it, but only found results claiming this didn’t work… Not actual scientific research, but better than “we think this should work, so now we’ll try selling it”
A software engineer that loves Disroot and the team behind it.
I tried searching for research on it, but only found results claiming this didn’t work… Not actual scientific research, but better than “we think this should work, so now we’ll try selling it”
I love this comment and Sun Tzu reference, thank you so much for posting it!
What is he holding? An ancient dildo or a shit stick?
Aah right, Kamasaurus Sex, my favourite!
And “Y” stands for “Your Mom”. But it was a one night stand…
I suspect it’s related to USA current affairs and have no clue what it’s referring to. Any hints for us outsiders?
I’m beginning to feel we’re no longer talking about Clean Code being bad, but about people following ideas they don’t understand, which is not related or caused to any particular book.
I hope your book won’t have a table of context and those stupid indexes. If they read it, they should know where you mention topics, right? Tables of contents considered harmful! /s
I’d love to learn what that damage was. I often see complaints (sometimes also involving tech choices) but usually they’re not specific, so I’m always left wondering.
First you confirm they have to spend a lot of time to set everything up, then you claim it’s just pressing a button? 🤨
Taking a picture with your phone maybe looks like that, when you don’t care, but knowing one’s gear and using it properly is already many levels above just pressing a button. Then only a few questions and one presses the button. Questions like: what will be blurred? what will stand out? how the picture will be composed? will colours play? or textures? are there relations between objects in the picture?
What in trying to say is: I don’t agree with you, that it’s just pressing a button. Programming is also just pressing buttons, right? 😉
C Tesseract has this interstellar vibe and brings quotes like the following, but with a totally different meaning:
I’m not going to argue, because I don’t know your work environment, but the notes I mentioned weren’t supposed to be published or attached to the product. They’re more of a personal knowledge base, where you can look up former approaches, issues found in the past, reasoning, decisions with context… All the zettelkasten tools out there do exactly that: help maintaining a useful knowledge base.
Staying here and reporting issues would help Lemmy, you know? Much more than just complaining it isn’t as stable and mature as a commercial product developed by a company for years.
That’s the next level of trolling!
That’s why we keep notes… Literate DevOps is a solution for my preferred editor, but there definitely are solutions for other tools too, even if they don’t work exactly the same.
I can’t recommend keeping notes too much.
Wait, you didn’t mean Emotion Regulation Act? Emotion should be regulated and distributed evenly within society!
Eat the emotional! ✊
I want people like you around me!
I’m trying to convince a senior developer from the team I’m a member of, to stop using copilot. They have committed code that they didn’t understand (only tested to verify it does what it’s expected to do). I doubt it’d succeed…
They’ve got Paid BSOD, I’ve got FreeBSD, we’re not the same.
That comment… Oh my, I want to joke and talk someone like you! Now!