980
top 50 comments
sorted by: hot top new old
[-] Aurenkin@sh.itjust.works 119 points 2 months ago

Don't worry half of those will be useless code comments

[-] kubica@fedia.io 130 points 2 months ago

// Here I'm not using that other thing that is now completely irrelevant, but I'll leave a comment to the non-existing thing anyway because I'm avoiding it.

[-] FishFace@piefed.social 19 points 2 months ago

REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE

[-] _stranger_@lemmy.world 26 points 2 months ago* (last edited 2 months ago)

The comment:

# This code does exactly what you asked: Never change state, only fetch the state and return the difference

the code: hallucinated database table drops

load more comments (1 replies)
[-] OwOarchist@pawb.social 101 points 2 months ago

Repeat after me: "Rejected. Reason: too large of a change for one PR."

[-] Solemarc@lemmy.world 97 points 2 months ago

I struggle to review a 1k line change. When people give me such big changes I normally don't believe they've reviewed them either.

[-] roofuskit@lemmy.world 67 points 2 months ago

That's because they haven't.

[-] marlowe221@lemmy.world 21 points 2 months ago

Mystery solved!

[-] Jesus_666@lemmy.world 19 points 2 months ago

Try working on a codebase that's all event-driven hexagonal CQRS with hand-crafted SQL for persistence. Add additional buzzwordy methodologies to taste.

Adding a single property to your product means you now have to update an aggregate class, several DTOs, and several event classes and handlers before you can even think about touching the UI.

And that's in your main solution. There's also at least one facade service you'll need to make compatible and you also need to update the event simulator used for testing. The latter night involve having to touch every single line in a 2000 lines long SQL script.

Having to go though three separate 600-2000 LOC PRs for one PBI isn't that exotic.

[-] bjc@scribe.disroot.org 10 points 2 months ago

forgive them lord, for they know not what they do

load more comments (1 replies)
load more comments (1 replies)
load more comments (7 replies)
[-] SubArcticTundra@lemmy.ml 89 points 2 months ago

The problem with Claude is that it doesn't write code to be modular & reusable. Every tiny change requires a complete rewrite.

[-] veryblandusername@fedinsfw.app 69 points 2 months ago

I've completely banned any code that can't be explained. I've had my CTO send me code at 3 AM to implement and when I ask him what I'm looking at he just says it doesn't need review, just push it.

Uhh, no sir, I'm not doing shit because you've handed me GCC and we're MSVC.

After I bitched endlessly to the CEO about that he said I have final say on what goes into the project.

[-] noxypaws@pawb.social 28 points 2 months ago

I've had my CTO send me code at 3 AM

I hope you don't even respond until your next normal working hours!

[-] veryblandusername@fedinsfw.app 17 points 2 months ago

I love my job, even when I have to deal with nonsense like that and I'm compensated very well to be on call 24/7.

[-] NocturnalMorning@lemmy.world 11 points 2 months ago

No amount of money would make me put my health at risk like that. Been there at a job before where I was always working. No thanks.

load more comments (5 replies)
[-] boonhet@lemmy.zip 11 points 2 months ago

we're msvc

Then switch to a real compiler on a real operating system, duh

load more comments (1 replies)
load more comments (17 replies)
[-] bdonvr@thelemmy.club 56 points 2 months ago

No

You ask your LLM of choice to look it over, completing the shit-cycle

[-] Supercrunchy@programming.dev 17 points 2 months ago

I fully expect this to become the new normal being pushed by management.

"We identified PR reviews to be blocking our newfound AI-powered efficiency, so we are now mandating all the reviews to done by AI. Also we figured all the developers are now useless since all you do is ask Claude to solve tickets, so you are all fired"

I wonder how long it takes for the first high profile disaster happening because of a policy like that.

load more comments (7 replies)
[-] skisnow@lemmy.ca 43 points 2 months ago

We've had a very recent uptick in engineers submitting PRs of hundreds of lines across multiple files, for Jira tickets that only asked for a one-line change. The engineers involved have been using AI assistants for nearly two years now, but there seems to have been a change in the last month or so in how aggressive the new models are at changing code.

[-] Blackmist@feddit.uk 59 points 2 months ago

Almost as if they're paid by the token...

load more comments (1 replies)
load more comments (3 replies)
[-] laurelraven@lemmy.blahaj.zone 39 points 2 months ago

That's an automatic reject from me, that's not a patch, it's an overhaul

load more comments (1 replies)
[-] AdamBomb@lemmy.world 36 points 2 months ago

🛑 Changes requested

Too big. Break into smaller individual PRs.

[-] yessikg@fedia.io 31 points 2 months ago

If you can't be bothered to write your own code, I can't be bothered to review

load more comments (1 replies)
[-] floquant@lemmy.dbzer0.com 30 points 2 months ago

It is not even peer review anymore, unless we are pretending that claude is our peer.

[-] Daywim@lemmy.world 30 points 2 months ago

Merge that shit, watch it all collapse, enjoy your forever holiday

[-] einkorn@feddit.org 13 points 2 months ago

"So, Daywim. Why did you let this obviously aweful PR pass your desk causing so much trouble for our company? I'm afraid we have to let you go because of this questionable performance." - Corporate

[-] EffortlessEffluvium@lemmy.zip 27 points 2 months ago

What part of forever holiday did you miss?

[-] einkorn@feddit.org 10 points 2 months ago

I interpreted it as "Holiday that lasts forever because the company can't work anymore" but I guess it is meant to mean "Holiday that lasts forever cause you got fired"?

load more comments (1 replies)
load more comments (6 replies)
[-] flb@reddthat.com 29 points 2 months ago

Our PR checks auto reject the PR if it has 1k changes

[-] Pika@sh.itjust.works 11 points 2 months ago* (last edited 2 months ago)

is it auto reject, or just doesn't auto approve and leaves it open for manual review

It seems weird that you can't do a pr at all with 1000 line changes, any moderate size feature addition could hit that mark

load more comments (4 replies)
load more comments (3 replies)
[-] EowynCarter@lemmy.world 23 points 2 months ago* (last edited 2 months ago)

Yep.

We have one PR still blocked. Last change is a simple comment from me “Why ?”

[-] grrgyle@slrpnk.net 11 points 2 months ago

The most important question that every change must answer.

[-] dylanTheDeveloper@lemmy.world 14 points 2 months ago

No Mr Bond, i expect you to approve

[-] einkorn@feddit.org 11 points 2 months ago

And people were already annoyed when I had ~90 changes due to refactoring and fixing imports ...

[-] CookieOfFortune@lemmy.world 11 points 2 months ago* (last edited 2 months ago)

If LLM can make big PR, LLM can split PRs

[-] ZILtoid1991@lemmy.world 12 points 2 months ago

The goal of AI providers is to make humans unable to maintain code, so you have to rely on their expensive subscriptions and tokens.

load more comments (1 replies)
[-] Psythik@lemmy.world 10 points 2 months ago

This is a joke I'm not college educated enough to understand.

[-] khannie@lemmy.world 22 points 2 months ago

It's basically saying "insert one ass loads of code in one go, all written by AI".

load more comments (1 replies)
load more comments
view more: next ›
this post was submitted on 11 Sep 2026
980 points (98.7% liked)

Programmer Humor

34233 readers
1811 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 3 years ago
MODERATORS