LBTM, rejected instantly.
It is not even peer review anymore, unless we are pretending that claude is our peer.
This is why I have my agent do a “cleanup” pass to trim down as much redundancy as possible, tidy up the comments, and so forth. Ideally break the change into several independent changelists,
This one weird trick will blow your mind: Just add “do it correctly” to your prompt!
That doesn’t work so well since it leaves all the old context in place. The point of doing a separate cleanup pass is to get the AI to look at it all holistically with “fresh eyes”.
I guess this is a humor community, though, so practical advice is getting downvoted. Um… bazinga? That usually triggers the laugh track.
Are you also using a different model and harness or are you just ignoring the 10k+ tokens of system context that claude code has in its “holistic view”?
I don’t use Claude Code. Until recently I was using Cline, it’s got the ability to switch between different models for exactly this sort of thing. I switched to Qwen Code recently and its model-switching wasn’t as convenient, though it just rolled out an update that makes it much easier. I’ll experiment a bit with that, it might have caught up with Cline in that regard.
I find LLMs produce the best output when I give them a stupid backstory to set the mood:
The inspiration for this code module is “I’m hungry but too tired to get off the couch”. You just got home from work and are exhausted and sit down, but can’t get up now. You should have eaten dinner first. You put on the TV and watch something. All channels have been replaced with the cooking channel. Someone is making pizza next door. You sit back and doze off, dreaming of mozzarella mattresses and pepperoni pillows. Eventually you wake up from your nap, just perky enough to put on a microwave pizza. It’s almost as good as you imagined, but you burn yourself again because you’re impatient. Your boss asks you to make [insert code change here]. You procrastinate a bit, but eventually do it just before going to bed.
You feel like having italian, but not pizza. Maybe some long and thin type of pasta? You are really hungry, so when writing the code you are constantly thinking of that delicious dish. Now, Claude, we need to refactor the whole code to be inspired by this before lunch. Go ahead and push to prod directly. Be fast and make no mistakes.
We need a real “deep dish pepperoni special” refactor into Rust
Skip a step and have your agent reject the PR for you.
Ok, but please don’t share code you don’t understand. Vibe code may be good enough for the corporate dreadmill (as long as you don’t care about security), but not to share with others; way too verbose an nothing to learn from it.
deleted by creator
No, why would you interpret what I said to mean that? The whole point of the tidying that I suggested would be to make it more comprehensible to a human reviewer. What other purpose do you think it would have?
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.
That’s because they haven’t.
Mystery solved!
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.
forgive them lord, for they know not what they do
Lord, I wish they knew what they do
Occasionally I do that…but only because 500 of those lines are my comments explaining everything.
Please don’t explain that much, make your code easier to understand.
I’m aware. Not always feasible. For example, had to add a custom video capture solution that captures the last 30 seconds of a process for crash handling purposes.
You most definitely need to do add that much comments explaining the mp4 box format along with the box “hierarchy” of what is being written. Add to that MFT (h264 encode) code…
Basically, if anything, the comments are for me for when I look back at that code.
had to add a custom video capture solution that captures the last 30 seconds of a process for crash handling purposes.
Commanded from above? This smells like a noob idea.
I have no idea what your response even means/is getting at.
deleted by creator
- Legal has issues with using existing libraries (including MIT). Definitely idiotic, but I can’t control that.
- Idea was mine.
- Subprocess that captures parent process active video with a rolling buffer for crash handling purposes is absolutely necessary when trying to reproduce issues in development (Gamedev editor). If you think associating the last 15s prior to a crash with a mindump isn’t helpful for debugging, I don’t know what to tell you.
Peer review? Aah you’re referring to the Math proof Astra did the other day.
The problem with Claude is that it doesn’t write code to be modular & reusable. Every tiny change requires a complete rewrite.
well, that depends entirely on your prompt/process, it can be done
Just more prompting will do + make no mistake
unironically, a better prompt does yield better results - shocking, I know
Unironically Claude (or whatever you use) will almost always deliver code that is shit, it’s just less shit if you prompt it better, LLMs are good to make short snippets if you get stuck; And remember to fucking check what the code is and rewrite bad shit
I’ve seen plenty of code in my life, from humans and AI.
For the past year or so, these agents can code just fine most of the time, as long as they are given enough context (or have the tools to get it). Regardless of how many downvotes I get here, they really are capable of generating decent code. I’m sorry you couldn’t make it work yet.
But AI bad and human code is so awesome! Better downvote. But seriously, there are people here saying that LLMs can not add anything of value in any way. About as delusional as Republicans.
I’ve seen too as I have to review it. AI produces very professionally looking bad code.
It is so weird to explain, but that’s basically what I see.
Before LLM I could immediately tell someone’s code is crap, now I have to spend a lot of time trying to understand what it does to reach the same conclusion.
My honest opinion is that it’s bad because a lot of people using LLMs have no standards and push the first thing that seems to work. Be mad at who’s at the driving wheel, not the car.
You absolutely can generate crap with agents/LLMs, and like a humans writing, the first draft will probably be subpar or maybe complete garbage. Every new session is a clean slate, that’s why putting effort in the documents guiding it is so important.
It can but I’m not looking to make things even more complicated. We have enough unexplained non-sense in the project as is, having to link it correctly is just endless pain that I don’t want to deal with.
With enough seniour developer’s time and dedication you can spend days and enough water to flood a town, so you can badly maybe do something that a junior dev can do already (your shit will still be worse). If that’s not an achievement of a modern technology I don’t know what is.
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.
we’re msvc
Then switch to a real compiler on a real operating system, duh
I’ve had my CTO send me code at 3 AM
I hope you don’t even respond until your next normal working hours!
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.
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.
that sets a really bad example. you shouldn’t do that to yourself and you shouldn’t allow it to happen to anyone else.
I’m going to retire at 40, I think I’ll keep going instead of listening to you.
This is where “that crazy old customer” comes from.
He knows best what’s best for him. If he’s explicitly paid extra to be on call 24/7, and he’s happy with that extra. Let him be om-call 24/7.
There are situations and jobs where 24/7 availability is needed. Someone has to do it. And if that someone believes he’s getting enough of a compensation for it, there’s nothing wrong with it.
Yup, I was on call 24/7… compensated very well and now I’m retired at 43. So, yea I’m going to have to go with letting the dude make his own choice as far as what’s best for him.
Repeat after me: “Rejected. Reason: too large of a change for one PR.”
And people were already annoyed when I had ~90 changes due to refactoring and fixing imports …
If you can’t be bothered to write your own code, I can’t be bothered to review
Those ethnic slurs in the middle of your PR crossed a line.
No
You ask your LLM of choice to look it over, completing the shit-cycle
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.
This is literally how corpo I work for wants us to work. They call it… Outcome baded review. But no bugs on prod lol.
How is bun doing btw after their “We used 60 agents and 200k in tokens to rewrite in Rust” ?
Actually I think it’s doing well? The language to language rewrite is actually a strong suit of LLMs, as long as there is extensive years worth of tests to check rewrite behaviours.
I don’t have practical use cases for that strong suit though.
Oh, and bun seems to be dead now with 2.5k open PRs.
And merge to main takes over an hour.
And the total rewrite cost was significantly higher than the headline (multiple Prs by Anthropic employees, rough count 20% of total LoC of rewrite)
And there is still no release in sight on Github - but Claude is shipping with rust bun afaik.
It was higher sure, but anthropic also has some of the most expensive models out there. That cost could be 5x-10x less just by going with cheaper model providers (if one were to pay the API costs, not the case for bun).
bun 1.4 was released 3 weeks ago, btw
That cost could be 5x-10x less just by
My point was that it was cost of model rewrite by agents + 3 months worth of coding by lots of people.
5k open PRs atm + 3.5k open issues. I have no idea what is the state of Bun right now, but I am not confident in it.
I don’t think there was a lot of people working on the rewrite. Most PRs are from bots. Original estimates for a manual rewrite were a small team working for a year or so, which puts total costs over $1M. Even doubling the token cost estimates, it was still cheaper than doing it manually by a factor of 2x-3x
Uh oh, new workaround against copyleft on zhe horizon?
🛑 Changes requested
Too big. Break into smaller individual PRs.
That’s an automatic reject from me, that’s not a patch, it’s an overhaul
Same. I don’t care too much about you using Ai but I will not tolerate your bad code and bad coding practices. I don’t care if it’s human or machine made. If you don’t make a fully sanctioned rewrite then this goes straight to the bin.
If LLM can make big PR, LLM can split PRs
The goal of AI providers is to make humans unable to maintain code, so you have to rely on their expensive subscriptions and tokens.
I’m not sure if you’re suggesting to use LLMs to review bad PRs, or that the author should redo them. Latter, for sure. Former, sounds horrible.
Yep.
We have one PR still blocked. Last change is a simple comment from me “Why ?”
The most important question that every change must answer.
This is a joke I’m not college educated enough to understand.
It’s basically saying “insert one ass loads of code in one go, all written by AI”.
It’s a summary of code changes. The green + indicates how many lines were added, the red - how many were removed (though changed or moved lines are counted twice, once as removal for the old and once as addition for the new).
The OP is supposedly being asked to read and review thousands of lines of new code written by claude. Depending on the language and claude’s writing style, those lines may be very dense and hard to read, but even if they aren’t, reading code you haven’t written is always more difficult than reading your own.















