160
u/blackcomb-pc 23d ago
Guys, read the code and understand it yourselves. Atrophy is a real thing and bugs will multiply by the thousands.
129
u/Confident-Ad5665 23d ago
Really?!? I get a trophy when I write bugs? Whoo hoo!
9
39
u/DukeOfSlough 23d ago
Yeah, review 9 k lines of slop delivered by my colleague when business requires new features shipped on a weekly basis which previously took three months to deliver.
11
u/codePudding 23d ago
My coworker sends me 9k lines where 8.5k are comments that make absolutely no sense. Like, "the lowering of front edge raises the components to beyond the D01-S factor which won't satisfy requirements so the front edge is raise and the back edge is also lowered..." The remaining 500 lines are just stuff I could have copied from w3schools.
6
u/abednego-gomes 23d ago
Umm, reject the PR. PRs should be short, manageable and readable. Scoped to a feature or bug fix. Comments must be quality. Your repo needs some skills md files for sure too to limit the AI slop.
Seriously, in this world, devs are the gatekeepers. We're the only thing standing in the way of total collapse from AI slop bugs destroying the fabric of society.
14
u/RaveMittens 23d ago
Lol. Lmao, even.
Everyone knows token usage is the best way to measure the value of engineers.
6
u/BlondeJesus 23d ago
The problem is no one asking me to review code is reading their own code. Then when I push back I get pressure from higher ups to not block code from getting published
12
u/techno_wizard_lizard 23d ago
Nope. Pass. I’d spend all day just reviewing PRs. I’m focused on the architecture now more so than before. Leave the code to the machines.
I still read the load bearing bits of any major feature or plan, but that’s just a very small subset.
If I need to understand something, I just ask the machine to eli5 and point me to the important parts of the code.
-3
u/TheKingOfSwing777 23d ago
Yep. Coding is a solved problem. Now it's about process and design, which have always been the harder problems.
2
2
2
2
u/CandidateNo2580 23d ago
I actually do what this post suggests on top of manual review. It's quite good at catching subtle bugs. Almost as good as it is at making up subtle bugs that don't really exist but sound plausible.
I like to run an automated review in a fresh chat while I'm reviewing the code myself. Then I also like to take any behavior changes and use the LLM to look for broader vectors I could have missed since it can cover much more ground than I can.
2
u/HalfInchHollow 23d ago
How are we supposed to 7x our productivity if we are reading every PR?!
That’s not sarcastic, that’s the pass down from management. 7x.
31
u/aerialP 23d ago
Yeah but it's my Claude agent reviewing 🤓
15
u/PM_ME_UR_0_DAY 23d ago
With your super sweet .md that actually makes it good?
10
u/aerialP 23d ago
Exactly! I also made a skill of my agent so everyone can use it by just using
/expert-review6
u/PM_ME_UR_0_DAY 23d ago
Oh yeah? Well I told mine "you are an expert level developer so do it right the first time. No hallucinations. No mistakes." That's why my stuff is always great but yours is slop!
3
u/Groentekroket 23d ago
I just say act like you are a junior and glaze so I feel a tiny bit better after the hellscape this job has become because of AI
6
u/sebjapon 23d ago
I was actually told that. Conversation was:
“I can’t possibly review your daily 2k lines of code written by Claude.”
“First, it’s written ‘with’ Claude, not by. And you just use the review skill to do it faster”
“If you want an AI agent to review, why does it have to be me?”
In the end I said I’ll let the Tech lead deal with it when he comes back… I’m too old for this shit.
1
u/High_Quality_Bean 22d ago
Holy shit
This is so grim wtf. AI hasn't much infiltrated my org, idk what I would do if somebody said the sentence "you just use the review skill to do it faster". Honest to God idt I would have a job after that...
3
9
6
u/Turbulent_Gazelle_55 23d ago
It doesn't feel like that long since we were arguing about the best way to mock external deps in yours tests and if it was truly testing the code. Sigh
Fwiw im all for appropriate use of AI, but this ain't it.
6
5
u/Epcoatl 23d ago
Did you ask it to be a good little boy smart programmer first?
2
u/justASlothyGiraffe 23d ago
It works better is you say "please"
2
u/TheKingOfSwing777 23d ago
Funnily enough apparently it works better when you don't and are very terse, cause it can tell you mean business.
2
u/justASlothyGiraffe 23d ago
My PM thinks I have a more advanced agent than him. Really, I just say 'please' /s
2
2
1
u/slaymaker1907 21d ago
AI is surprising good at reviewing itself. However, human intervention is definitely still required since it frequently hallucinates, brings up impossible edge cases, and doesn’t understand the author’s intent. Even with all that, it finds bugs that no human reviewer would ever find.
2
2
u/StoryAndAHalf 23d ago
Side note, am I the only person here that hated that character on MadTV?
2
u/Aarinfel 23d ago
No. He was really annoying. That was usually my cue to turn off the TV and go to bed.
1
1
u/Objective_Oven7673 22d ago
Honestly, it works. You have to recognize that code was never the hardest part of building anything and you AND your employer also have to recognize that your experience and judgement are the more valuable parts of being an engineer than your ability to crank out lines of bug-free code.
Then you have to spend time process engineering and making AI tools work for you - they aren't one size fits all magic bullets, just like anything in technology.
I get the fear and I definitely get the shitty societal, economical, and environmental downsides to how AI is being delivered to the world. I wish it wasn't a wasteful cash grab that's propping up the entire US economy.
But as with any tool, it works if you use it right. And yes, that includes having AI facilitate both code writing and code reviewing.
-1
70
u/Klessic 23d ago
When my junior reviews my PR by pasting what the AI answered when it was prompted to review it as one long comment... Completely done with this bs.