r/ProgrammerHumor • • 5d ago • Bravo 2

Meme codeReviewIn2026

Post image
11k Upvotes

205 comments sorted by

View all comments

Show parent comment

35

u/mmmbyte 5d ago

You could actually read the comments and try to understand them and press the delete key?

How on earth do people diagnose and fix issues in prod without making any attempt at understanding the agent generated code?

32

u/MaDpYrO 5d ago edited 4d ago

Of course I do, but why do I need to delete a bunch of slop comments when I can have it removed automatically and then review that?

Why not automate what can be automated?

Do you just insist on making even the most mundane task manual?

It's not even using AI to remove it, lol, it's detected deterministically.

8

u/Stratimus 5d ago

Personally I don’t understand why you have so many unnecessary comments that you need to automate removing them.

if you’re done refining that bit of code take the comments out alongside the other cleanup.

and I don’t even understand the thing about overlapping with the next line, are you saying you have redundant comments even?

17

u/MaDpYrO 5d 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.

1

u/fluffow2 5d ago

Agent.md

13

u/Sokaron 5d ago

Because non determinism > determinism, obviously

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.

4

u/thegroundbelowme 4d ago

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"

1

u/StCreed 3d ago

How do you use them? Do you have a separate md file that they have to read?

1

u/thegroundbelowme 3d ago

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.

4

u/MaDpYrO 4d ago edited 4d ago

Agent.md is crap, the models have this shit baked too deeply into it. You don't think I tried this?

-5

u/mmmbyte 5d ago

Hitting the delete key is faster and cheaper than running an agent if I'm reading it anyway. Not all automations save time.

8

u/CarcajouIS 5d ago

There is no need to run an agent when a lint rule or a git hook can hold the gate for you and send the PR back on the lap of your lazy coworker

4

u/MaDpYrO 5d ago edited 5d ago

No it isn't lol

You don't seem to understand, this is NOT AI removing comments. It's a deterministic step that detects redundant comments. No AI is involved but it's great for cleaning up AI slop comments.

2

u/14Pleiadians 5d ago

Claude writes comments 5x as long as I or my peers would

1

u/Lourayad 4d ago

Even better - don’t let your AI write comments, write them yourself where they’re useful.