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? 😉
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 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'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...
I'm not ignoring the other two things listed, I'm realistic.
You described it like it was something rare for FAANG to do bad things. Or like it was bad only when it required whistleblowing... Think how many things got crushed by EEE tactics, and it's only one class of examples of why big tech is inherently bad.
You could say the same about eating meat or any other cause. What's the difference, the animal is already dead anyway, right? Well, it's not that simple.
Thanks to the growing number of people who eat less or no meat at all, meat production is decreasing. If all of them kept saying that one man boycott makes no difference, the change would not come.
If you can't find a better job - fine, work for the evil FAANG or whatever. We live in capitalism and it's clear we need to work somewhere. But at least be honest and don't look away from inconvenient truth. There's still something good you could do while keeping the job at $evil_company. For example, you can support financially those who haven't got nice jobs in IT.
Aah right, Kamasaurus Sex, my favourite!