2 ms·
Disagree. At least back in the day there weren't endless comments about how this widget is load-bearing, and how honestly the other widget carries the derived w
by OptionOfT 6d ago
Disagree. At least back in the day there weren't endless comments about how this widget is load-bearing, and how honestly the other widget carries the derived widget, referencing decision ADR-100 that is nowhere to be found. All these comments matter because once accepted as part of the codebase the next LLM takes these comments as canonical.
The largest problem these days is the volume of code developers are expected to review. The volume went up significantly.
- Daishiman 6d ago> At least back in the day there weren't endless comments about how this widget is load-bearing By far the biggest problem 90% of developers have with AI is that they should be turning off comments, as it's clear that the training data they have is no good for developing a theory of mind for an engineer who has to read them. I've turned them off and add them myself at review time and am quite happy.
- zahlman 5d agoRequiring the coding agent to (try to) iterate on code clarity until comments are no longer necessary, probably doesn't hurt either. Save the commentary for conversation logs, agent Markdown files, and other sorts of documentation.
- theshrike79 5d ago> the next LLM takes these comments as canonical This is the best and worst thing about LLM coding agents. They trust comments way too implicitly. And then the errors just keep compounding. Or a temporary hack that becomes "load-bearing" because the agent doesn't figure out that it's supposed to be a temporary testing shim - instead it keeps building on it until it basically duplicates what it's mocking.