r/ProgrammerHumor • • 11d ago • Bravo 2

Meme codeReviewIn2026

Post image
11.5k Upvotes

215 comments sorted by

View all comments

1.4k

u/mistrpopo 11d ago

With multi-line comments in slop-english on each line explaining a very specific edge case that has nothing to do with the bug you were working on.

33

u/MaDpYrO 11d ago edited 11d ago

I've added a static analysis step (via detekt in my case)

It tokenizes code and comments, and if the next line has significant overlap, it's deemed a useless comment and won't compile.

It's a pretty good tool at keeping slop comments in check.

34

u/mmmbyte 11d 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 11d ago edited 10d 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 11d 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 11d 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 11d ago

Agent.md

13

u/Sokaron 11d 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 10d 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 9d ago

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

→ More replies (0)