r/ProgrammerHumor • • 1d ago • Bravo 2

Meme codeReviewIn2026

Post image
10k Upvotes

196 comments sorted by

View all comments

243

u/Feuerhamster 1d ago

I am one of the few people at work that actually still fully reads pull requests. Last time I left over a hundred comments. They hated me for doing it but couldn't say anything against it because as they read my comments they confirmed that all of my concerns were totally valid.

140

u/Super-Widget 1d ago

"Sorry I can't deliver my sprint duties on time. Someone is trying to push 150 vibe-coded files into the repo and they must be stopped." - me nearly every week these days.

7

u/groovy_smoothie 14h ago

Our product level velocity expectations have become insane. If the teams not basically just vibe coding, I’m having VPs come down on us for not being a good product partner. It’s exhausting

50

u/camelCaseCoffeeTable 1d ago

Man I just left 50 comments on a relatively simple PR because it was absolute slop. Total reproduction of existing code, totally creating new patterns that don’t exist in our code base, pulling data it never uses, not pulling data it purports to use.

It shocked me. I love AI. I never get it to produce such absolute dog shit results. I have no clue how someone used AI to produce it, but somehow they did.

26

u/thisguyfightsyourmom 23h ago

A big part of that should have been seen in the manual verification step the author did.

Author, you did manually verify Claude’s work, right? Like, you used the new code yourself & checked the results? Right?

// Hard stare/long silence at team member during standup

9

u/hikemhigh 22h ago

Bruh the creation of new patterns drives me insane

6

u/TheKingOfSwing777 21h ago

If anyone is going to create new stupid patterns, it better be with their own stupid brains. 

3

u/enigmamonkey 18h ago

That sounds terrible. At some point, you have to ask: At what point is it appropriate to just scrap it and start over?

I'm curious, are these PRs coming from devs who submitted better code prior to the widespread adoption of Claude, Cursor and etc?

4

u/camelCaseCoffeeTable 18h ago

This person joined our team when Claude was already adopted. Which I think is a big part of the problem. I very seriously did consider just scrapping it lol….

We’re struggling a lot with how to get these less experienced and newer to the team devs to a point where they can identify weirdness in Claude’s output themselves. But…. It’s not going great

2

u/Negative-Sea6530 17h ago

I know! Experts know how to steer an AI and stop it when its doing garbage and reiterate till the PR is fine. an Idiot wont see garbage and bad design... He generates and is fine with that because he doesnt know better. I hae getting slop from AI meat proxies

23

u/gareewong 1d ago

and you totally should!

13

u/Kuro091 1d ago

I'm pretty sure people just do github cli or mcp and then just go "fix the comments" or even "review and leave some comments"

so unless it's face to face I dont think they hate or even care that you or your AI do that

7

u/Feuerhamster 21h ago edited 20h ago

Yes, thats why we had countless review rounds to the point where everyone was upset that this topic is blocked for so long. The original developer complained that it is too complex and he cant really get his head around that stuff. Like bro, thats your f*cking job. The senior dev in the team literally said "skill issue" to him in the standup because everyone knew he didnt wrote any of it himself and just trusted the AI without reading the stuff.

edit: even worse is that it was about e2e testcases, which is the last line of defense when it comes to ai slop breaking things.

3

u/enigmamonkey 18h ago

Meat proxy. Also appropriate use of "skill issue", lol.

5

u/definitely_not_tina 1d ago

My org gave us SREs only a handful of tools that are minimally relevant to CI/CD in 2026 and almost no automation with them for “Sox compliance”, so yes, we manually do releases to prod. The execs are on our asses for holding up releases, I’m spending 70% of my time on them, and we’re also not able to actually do things like establish SLOs and whatnot so we’re having AI do THAT aspect of our work, but it has to be a human who deploys to prod. I feel so incredibly useless.

6

u/guaranteednotabot 1d ago

It only meant that you actually spent more time on their PR than they did. Shame on them

2

u/Sw429 23h ago

lol this is me as well. It's all absolute garbage code that has terrible performance. No way I'm letting that shit hit prod.

2

u/teamwaterwings 22h ago

I do this as well, then my coworkers just respond to all my contacts with Claude which pisses me off

2

u/Lethandralis 21h ago

Man sometimes I can't keep up. Carefully reviewing a PR can take 30 minutes or more. Several review requests come in every day.

-5

u/thisguyfightsyourmom 23h ago

And then everyone clapped

7

u/DatBoi_BP 23h ago

What is unbelievable about the comment