Some of you people are so autistic it needs to be spelled out for you. Being with people who aren't good for you in other ways is similarly terrible. I cited one extreme example and that's the only thing you focus on.
It could be as simple as someone who isn't supportive ever.
And no, the person that tried to kill me wasn't abusive otherwise. She was just very unstable.
That's exactly what happens in some organizations. I couldn't believe it the first time I saw it, but it is what it is. And the reason is some bosses are addict to consensus. Infuriating but there's really no other option than shrugging off the problems, waiting for staff changes or looking for another job.
Aside from the origin, there're situations in which you need to somehow shave the yak.
Yes, it's about procrastination, but not of the task at hand. You procrastinate in some older task that's really blocking what you need to do now.
It's chain procrastination. Oldest task blocks older task that blocks old task that blocks current task. It's evil because it overflows the task planning buffer. Also you get used to say nah when you start to think in a task in that general direction.
Maybe you should shave the fricking yak already. Or maybe you should use fake yak hair, idk.
The thing about the Mikado method is that you’re taking what from your perspective is a top down task and flipping it to bottom up. Which is for instance more amenable to refactoring, which is a bottom up task.
Sometimes when you get to the bottom you discover a shorter route backup to the top. The trap is that since you “already wrote the code” is seems a shame to delete it. But that code hasn’t been reviewed or vetted and “code is not the bottleneck”. You really do want to delete it because there’s a new version that’s 1/3 the code, and touches less of the existing system, and so will take less work to review and vet.
Thank you, I had not hear of that method (my comment was more about wetware) but I doubt it will be unfamiliar to me, I've done everything refactor related, mostly successfully... when they let me (see https://hackernews.hn/item?id=47163985 )
IMHO, the key is where you add complexity. In software you have different abstraction layers. If you make a layer too fat, it becomes unwieldly. A simple system evolves well if you're adding the complexity in the right layer, avoiding making a layer responsible for task outside its scope. It still "works" if you don't, but it's increasingly difficult to maintain it.
The law is maybe a little too simplistic in its formulation, but it's fundamentally true.
A couple of different uses of AI, recently detected in YouTube:
1. There are channels specialized in topics like police bodycam and dashcam videos, or courtroom videos. AI there is used to generate voice (and sometimes a very obviously fake talking head) and maybe the script itself. It seems a way to automatize tasks.
2. Some channels are generating infuriating videos about fake motorbikes releases. Many.
"Mostly because of the continuous attempts to force Copilot usage for our repositories, Gentoo currently considers and plans the migration of our repository mirrors and pull request contributions to Codeberg."
You can throw the arrow with just a piece of rope rolled around your hand and using the same grip as in the atlatl. Romans called those slingshot arrows tragulae.
Congratulations.