AI Weekly Malaysia

Back to items Summaries

Harvard researchers find AI coding agents shifted the bottleneck to code review

ID
48153
Status
summarized
Published
18 Nov 2026, 5:16 AM
Fetched
19 Nov 2026, 9:23 AM
Provider
Hacker News
Category
dev-community
Original URL
https://complexdiscovery.com/harvard-researchers-find-ai-coding-agents-shifted-the-bottleneck-to-code-review/
Source URL
https://hnrss.org/best

Summary

Score
8.5
Created
19 Nov 2026, 9:23 AM
Tags
Audience
developersvibe_codersai_agent_usersstartup_founders

What happened

A Harvard working paper by Ph.D. candidates Fiona Chen and James Stratton, covering 718 firms and 725,938 workers, found that teams adopting AI coding agents wrote roughly 30% more code but saw no detectable rise in finished work, while code review time rose 49%. The study is a job-market paper with no completed peer review, and it was built by joining Jellyfish engineering-analytics data to LinkedIn employment records. It drew 319 points and 435 comments on Hacker News.

Why it matters

If you are paying for coding agents, the constraint you should budget for is reviewer attention, not token spend: in this sample 30% more code produced no measurable gain in shipped work while review time grew 49%. Concretely, that argues for capping agent-generated diff size and tracking review turnaround time as your adoption metric instead of lines generated or PRs opened. Read the numbers with the methodology in mind, since the activity data comes from a vendor analytics platform joined to LinkedIn records, and treat the 49% as a hypothesis to test against your own repo rather than a settled result.

Discussion angle

The study measures output with vendor activity analytics that lean on code-volume proxies. What would you measure instead in your own repo to tell whether agents actually help, and where would you put the cap on agent-generated diff size so review does not become the queue?

Top