[kevincox]

Yes, I especially see this in code comments. You will get a PR where the comments reference an approach that wasn't the previous state and isn't the state of the PR. You can basically hear the dev telling Claude to take a new approach and now it is so fixated on the old approach being wrong that it litters the whole patch with traces of it despite now being irrelevant.

[greengreengrass]

Exactly this. Most of my time writing code is now not necessarily spent writing the said code, but going through whatever Claude or some other agentic process produced and tidying the comments to be less temporally sensitive to the conversation that produced it.

The problem is that process of not writing the code, but just editing what the LLM produced – and somewhat mindless editing at that (I'm editing comments, not LoC!) – leads to a loss of focus and all the perils of human procrastination that entails (hello, writing comments on HN).

I've tried to prompt Claude et al. not to do this - but whatever I've tried so far, even meta-prompting it to ask why it ignored my instructions, it doesn't work, doesn't stick, and I can't find a good way to stop it.