Debate flares over AI code review automation: bottleneck or mistake?
PostHog and others pitch agents to replace human code review; critics warn it abandons the last safeguard against LLM-generated sprawl.
What to know
- PostHog advocates using AI agents to review code generated by other AI agents, framing human review as a velocity bottleneck that automation can solve.
- Critics argue code reviews serve purposes beyond bug detection—establishing team ownership and maintaining codebase understanding—and that automating them away treats the symptom (review speed) rather than the disease (unsustainable code generation volume).
- Pressure is mounting on individual reviewers to accept lower standards as LLM output surges; debate centers on whether restricting AI contributions or automating reviews is the right response.
- The conversation parallels earlier waves of automation (music production, manufacturing) where increased output volume did not guarantee quality gains.
The dispute Whether code reviews are primarily a correctness check (solvable by automation) or a ownership/maintainability safeguard (requiring human judgment and context). · positions read across 7 posts and comments
AI agents should automate routine reviews to free humans for high-value work and reduce context switching.
-
“Something like 60% of my token spend is burned automating the toil of handling CI and review and I don't regret a single dollar.”
Paul D'Ambra · PostHog newsletter ↗
Code reviews serve ownership and maintainability functions beyond correctness; automating them is a mistake that avoids fixing the real problem: unsustainable velocity.
-
“All of that seems to be based on a very wrong premise: code reviews is primarily a mean of establishing the code correctness.”
popzxc · Reddit (blog crosspost) ↗
The real solution is to limit LLM code contributions and hire more senior reviewers, not automate reviews away.
-
“the only way to do this is ban LLM code contributions. Their output simply outscales any review process. You're correct that the code review is essential so that someone else can own the code.”
torsten_dev · Reddit ↗
Teams using LLMs successfully maintain review rigor and cultural discussion rather than accepting management pressure to ship more.
-
“In my teams, likely, there is a consensus that LLMs are meant to improve quality more than velocity. And maintaining it this way is certainly a process.”
popzxc · Reddit ↗
PostHog Developer tools companypopzxc Software engineer and criticPaul D'Ambra PostHog engineer
How it unfolded 4 developments, newest first · click a bar or a number to jump postscomments
-
4
PostHog publishes workflow guide for agent-driven code review
PostHog's newsletter published a guide detailing how to use AI agents to review code faster, framed as removing the human reviewer as a bottleneck. The piece recommends deploying multiple agents with different instructions to handle routine reviews, flagging only complex PRs for human attention, and automating adjacent tasks like CI monitoring and test re-runs.
“The 500 IQ take is for developers to review as little code as possible.”
— PostHog newsletter -
3
Developers propose restricting LLM code contributions rather than reviews
In response, some engineers argue the only sustainable solution is to ban or severely limit LLM code contributions, rather than trying to automate reviews to keep pace. One commenter states that code review can only work if humans are reviewing human-written code, and suggests hiring more senior reviewers instead.
“the only way to do this is ban LLM code contributions. Their output simply outscales any review process.”
— torsten_dev -
I've said it many times, look back to music at the turn of the century (feels weird to use that term about something I was already in my 30s for.) There are so many parallels. The sudden influx of ever more powerful digital audio manipulation tools vastly speeded up the production of music. But it didn't magically create a lot more great…
2 more of the top 3 · 5 posts in this stretch
-
I can feel that. In my teams, likely, there is a consensus that LLMs are meant to improve quality more than velocity. And maintaining it this way is certainly a process: we have built a culture of discussing news, approaches, etc in _both_ ways -- if something looks cool, we might try it or someone can even explain their experience to everyone; if…
-
developers to review as little code as possible AI companies don't want to hear this, but the only way to do this is ban LLM code contributions. Their output simply outscales any review process. You're correct that the code review is essential so that someone else can own the code. Static analysis, cursory code review, grep on steroids, whatever…
-
-
2
Team leads and engineers voice strain from LLM output volume
In Reddit comments, engineers describe the pressure to lower review standards as LLM-generated code volumes surge. A team lead reports struggling with demands to accept lower-quality changes and more hand-waving about maintainability concerns, while acknowledging that requests for granular changes result in 'more slop.' Others draw parallels to earlier technology waves where automation increased output without increasing quality.
“I've found it increasingly difficult to handle the firehose of LLM-generated changes, so I am on the receiving end of this pressure to lower review standards.”
— ConnaitLesRisques -
Good article, thanks for sharing your thoughts! I’m a team lead and we’ve always had a strict review process on "my" projects. Lately, I’ve found it increasingly difficult to handle the firehose of LLM-generated changes, so I am on the receiving end of this pressure to lower review standards. I’m really struggling with how to deal with that. I’ve…
1 more of the top 2 · 2 posts in this stretch
-
Wait you think PR reviews are a problem that’s solved by writing code by hand? You’ve never dealt with devs who put out atrocious 1k line PR “they spent a whole sprint working on” that doesn’t fit into the architecture but the moment you say something they run to their manager to complain and in the end their team closes this PR, opens identical…
-
-
1
Engineer publishes critique of AI code review automation trend
popzxc published a detailed blog post arguing that recent proposals to remove or minimize human code reviews—including from PostHog, Intercom, and Anthropic—are fundamentally misguided. The post contends that code reviews serve purposes beyond detecting bugs, including establishing team ownership and codebase understanding, and that the real problem is unsustainable velocity, not the review process itself.
“All of that seems to be based on a very wrong premise: code reviews is primarily a mean of establishing the code correctness.”
— popzxc
What people are saying 2 voices from 1 site · best of 7 · verbatim
- If LLM output outscales any review process, is the answer to automate reviews or to restrict LLM contributions?
- What does team ownership of a codebase mean if humans no longer review the code they maintain?
- Sep 21
-
Manual lathes -> CNCs, custom assemblies -> Ford Model Ts, there's a dozen other examples of automation where quality matters more than most software, and automation changed the whole process. We are not unique Except we are unique. Copying software is costless. Copying a model T costs a lot. Try understanding the limits of a metaphor before…
-
Wait you think PR reviews are a problem that’s solved by writing code by hand no. i think the problems caused by AI written code that people think can be solved at PR review time are solved by writing the code by hand. You’ve never dealt with devs who put out atrocious 1k line PR of course I have and now this problem is twice as bad . i think…