> Then this one really is a pattern that creates a lot of churn: > - Add a small, to the point, comment... As if you even need to tell Claude to add comments.

> Then this one really is a pattern that creates a lot of churn: > - Add a small, to the point, comment... As if you even need to tell Claude to add comments. Over the past few weeks I've noticed Claude over-commenting everything. Massive PRs where you realise that fully half or more of the lines that have changed are comments. It's no good at all: it just pollutes the context, causes token churn, ablates quality, and makes getting to a high quality outcome considerably slower and more expensive. I get that sometimes knowing why a thing is the way it is can be useful and valuable, but this is what commit comments are for in my mind. I've had to tell Claude to stop commenting code because the behaviour has become so problematic. > The what _is_ the code. Exactly. If I don't know what the code does because it's arcane and not commented I can simply ask the LLM to explain it to me. I don't need an essay in comment form.