Same here...
We commit bad decision, then in the next PR, workaround the bad decision (instead of undoing it), then in the next PR we have to workaround (aka deal with) the initial bad decision + work around...so on and so forth...
And at any point, manually reviewing the changes becomes impossible because you have to reason about the changes keeping all the workarounds and special cases in your mind...
I'm convinced that LLM-generated comments accelerate this problem, because they embed twists that a human didn't choose, and then those affect what gets generated next.
Much the same way LLM-characters don't do so well at answering "I don't know", there's a problem of them failing to cull context.
Code is easier to look at/read that way. I skim the README, then read the code.
Otherwise code comments are just nuts and unmanageable, because there's no hard/enforcing feedback loop on those. They can contain anything, even non-sensical things, old information/decisions, history of development, wrong information, contradictory information, and code still compiles. There's no pressure to keep them in check.
Lint step that fails build if code contains long comments is also useful as a hard-constraint.
> What has made me enjoy it less, is having to deal with colleagues' use of it.
In fairness though I never really enjoyed programming for the sake of it, I was always about what you’re getting at the end.
The correct response to "I feel I have been promoted (without a corresponding title or pay change)" is to be pissed off, not excited
A promotion is only a good thing if you actually benefit from it
LLMs are for people who want to turn off their brain. If you want your team to improve, you should lead by example and stop using LLMs. You need to create an environment where it is unacceptable to turn off your brain. Your underlings will never use LLM tools the way you want them to. LLM tools are designed to be used the way your underlings use them.
P.S.: An employee discovered, five minutes after deployment, that click events are not properly handled in one of the app's buttons, leading to visual and behavioral glitches.