Harvard researchers find AI coding agents shifted the bottleneck to code review
judahmeek
129 points
177 comments
November 17, 2026
Related Discussions
Found 5 related stories in 229.3ms across 13,334 title embeddings via pgvector HNSW
- AI coding agents generate more code, but not more software gumby · 326 pts · October 12, 2026 · 69% similar
- Coding expertise is going to collapse from AI reliance larsfaye · 503 pts · August 24, 2026 · 64% similar
- AI Coding and Its Discontents polymorph1sm · 13 pts · August 10, 2026 · 64% similar
- AI makes programming differently difficult tchalla · 146 pts · July 21, 2026 · 63% similar
- 80% of developers find AI coding more addictive than helpful theanonymousone · 13 pts · August 22, 2026 · 62% similar
Discussion Highlights (20 comments)
judahmeek
I've submitted the original paper ( https://fion.ac/jellyfish.pdf ), but others already have to little engagement, likely due to the paper's terrible title.
u1hcw9nx
This again increases the demand for good programmers. Write only programmers are dime on dozen. Those who can read code written by others (and themselves) and analyze it are harder to find.
gzell
From real-world experience, I have to disagree. It always has been and continues to be a faulty, up-front specification problem. The tail don't wag the dog.
jsrozner
We needed a research paper to tell us this?
root_axis
I'm being told the answer is simply to let AI review and merge the code. Problem solved.
dangoodmanUT
This feels obvious to me, but it's interesting how so many people feel the opposite. I guess it depends a lot on how a company manages their SDLC/bureaucracy
jacobgorm
The problem is that when nobody writes code or feels ownership over it anymore, nobody will be qualified to or really interested in doing the code reviews. The way forward could involve dropping code reviews altogether. You could argue that the useful pingpong between coder and reviewers has been replaced by the similar pingpong between the prompter and the agent.
wewewedxfgdf
But people keep saying "coding was never the bottleneck!".
wewewedxfgdf
Test don't review.
ttctciyf
Vaguely reminiscent of the classic trope around 70's computer "effficiency gains" where a newly introduced computerised accounting system would end up taking longer than the original human-run system because once the computer was through doing the books the original human bookkeeper must still check the results manually.
avereveard
Harward researcher read lovable blog post
lz400
A lot of this university research on AI feels dated. This is something we all faced months ago. Many times they're also reaching conclusions using obsolete models, etc. Feels like things move too fast for traditional research cycles to catch up to AI dev
dominotw
No pull request in my company get any human review comments anymore. No one is reading.
JonoW
Maybe we should just review the prompt(s) the PR author used. Would be nice if this was automated and included in a PR. So code review is really checking that the inputs were valid, and testing the outputs.
TexanFeller
"code is cheap"...if you don't need to understand, review, and maintain it as part of a team.
nout
That's sort of old news. Code isn't manually reviewed anymore much.
inshard
In other news, Dartmouth researchers find the sky is blue.
thom
I really think ‘shifted the bottleneck to code review’ is misleading. It’s bad code. They write bad code. Yes if you want to salvage it you do a lot of code review, but that’s only because you’ve set your process up to pick spaghetti off the wall against which it has been flung. You could easily just push it all live without review and then pretend the bottleneck is SRE time, or set fire to yourself and claim the bottleneck is emergency service response time. But the root cause is that it’s bad code.
sinsterizme
Maybe 6-12 months ago when everyone was reviewing in the same way we did pre AI. Nowadays agents write better code than most developers so it’s more about catching design or integration issues. I think the bottleneck in the long term will be feature prioritization and specification, and testing. My role has already shifted a lot more into more CI checks to keep LLMs on guardrails
diego_moita
I find funny that every time we discuss code made by AI people's reaction is to nurture some feeling of "someday, somehow they'll regret Claude Code and come back to me". I suspect that the old assembly programmers had the same hope and feeling about the first higher level compilers for Ada, Pascal and C. And guess what? There are very few assembly programmers these days. AI code is here to stay and will only grow. Deal with it. More than in any other area it is quite silly to be a Luddite in IT.