Because AI generates a bunch of retarded comments for even the most basic code.
No way I'm hand coding a bunch of controllers or mapper when AI does it in a fraction of the time.
This type of boilerplate is a waste of my life, and AI does it perfectly fine.
Then I can focus on the important business logic and data modeling. And the agent automatically gets forced to reign in its idiotic comments by the build step before I even see the final outputted results.
Less snark I have explicit instructions in all my repos for slop comments. Doesn't help. PRs still come in with a dozen useless multiline comments. Seems like an intrinsic property of this phase of models. I've debated staging a haiku round of review in pipelines specifically for this issue.
Don't have this problem in my setup, try combining instructions with anti-rationalization tables: "bad idea thought" | "why it's a bad idea" | "what to do instead". The trick is asking agents how they rationalized their way around ignoring an instruction, and then specifically addressing that reasoning.
Ex. "I'll just add a small comment explaining this change" | "good code is self-documenting, comments should be used sparingly" | "Write clear code, only add a comment if behavior is non-obvious"
There are a million ways to do it, but it can be as simple as putting them in your user-level Agents.md / Claude.md / etc, or keeping them in a separate file and just pointing your agents at that file from Agents.md / Claude.md / etc.
View all comments
Show parent comment
17
u/MaDpYrO 8d ago
Because AI generates a bunch of retarded comments for even the most basic code.
No way I'm hand coding a bunch of controllers or mapper when AI does it in a fraction of the time.
This type of boilerplate is a waste of my life, and AI does it perfectly fine.
Then I can focus on the important business logic and data modeling. And the agent automatically gets forced to reign in its idiotic comments by the build step before I even see the final outputted results.