@rohanpaul_ai: MIT study. Code volume surges by 300%, but output increases by only 30%: The AI dividend meets an awkward reality. They…
Summary
An MIT study of over 100,000 GitHub developers finds that AI coding tools increase code volume by up to 300% but only boost shipped software by 30%, highlighting bottlenecks in human review and integration.
View Cached Full Text
Cached at: 06/27/26, 07:54 AM
MIT study. Code volume surges by 300%, but output increases by only 30%: The AI dividend meets an awkward reality.
They studied 100,000+ GitHub developers and find that AI coding agents massively increase code production, but much less of that work becomes shipped software.
Autonomous AI coding agents raised commits by 180%, but releases rose only 30%.
The paper’s main idea is that software production has weak links, so faster code writing does not help as much when humans still need to review, connect, test, package, and ship the work.
The authors also check app marketplaces and find more new apps, but no increase in total usage, which means more software appeared without clear evidence that users adopted more software.
The marketplace evidence points the same way: more new apps appeared, but total usage did not rise.
The authors compare more than 100,000 GitHub developers before and after they start using 3 generations of AI coding tools, from autocomplete to more independent coding agents.
Autocomplete raised commits by 40%, interactive coding agents raised them by 140%, and autonomous coding agents raised them by 180%.
The 180% commit gain shrank to 50% for the number of projects and 30% for actual releases.
The estimated “elasticity of substitution” is 0.25 i.e. for every big improvement in AI’s usefulness, only a small amount of human work can be replaced.
Because AI can write code faster, but humans are still needed to decide what to build, check if the code works, connect it with the rest of the product, fix messy edge cases, and actually ship it.
papers .ssrn.com/sol3/papers.cfm?abstract_id=6859839
The top 1% of U.S. AI firms are now spending about $7,500 per employee each month on AI.
Source: econlab .substack.com/p/how-much-does-it-cost-to-be-ai-pilled
Similar Articles
For every $1 spent on AI coding tools, only $0.18 reaches production. Analyzed 1M+ PRs to find where the rest goes.
A study of over 1 million pull requests found that only $0.18 of every dollar spent on AI coding tools reaches production, with the rest going to bug fixes, rework, and review. The analysis shows that while PR volume grew 2.6x, reverted PRs grew 3.7x, indicating failures scaling faster than output.
Agentic Code Review (15 minute read)
An analysis of how AI coding agents have shifted the bottleneck from writing code to reviewing it, with data showing a 861% increase in code churn and a rise in defect rates, making code review the most leveraged skill in software engineering.
@thinkszyg: The AI Coding Speed Paradox: Coding 48% Faster, Review 6x Slower. How to Rebuild the Review Process? SD Times Analyzes Data from 250,000 Developers: AI Boosts Coding Speed by 48-58%, But AI-Generated PRs Get Stuck in Review for 4-6x Longer…
The article points out that AI coding increases coding speed by 48-58%, but code review time increases by 4-6x, and security vulnerabilities also rise. It proposes a three-step plan to rebuild the review process: AI pre-review, focusing on architectural decisions, and using Microsoft's open-source ASSERT framework for behavioral verification.
Revised: Estimated share of newly written code exposed to AI generation and review
This paper revises the estimated proportion of newly written code that is generated or reviewed by AI, analyzing its impact on software development.
@danshipper: GitHub has a front-row seat to how code is changing now that everyone—and their army of agents—can ship code. In March …
GitHub COO Kyle Daigle discusses the surge in AI agent-created pull requests (17 million in March) and the projected 14 billion commits this year, emphasizing open-source maintainer control, usage-based pricing over per-seat licensing, and the collapsing developer/non-developer distinction as AI tools enable non-developers to build apps.