Code 2025
Can you prove AI ROI in Software Eng? (Stanford 120k Devs Study) – Yegor Denisov-Blanch, Stanford
Yegor Denisov-Blanch , Stanford
Overview
This talk explores the impact of AI tools on software engineering productivity, questioning whether current enterprise adoption is driven by genuine ROI or hype. Research spanning two years and multiple companies uses a machine learning model, trained on expert evaluations of code commits, to measure productivity gains. Initial findings suggest a median productivity increase of around 10% for AI-using teams, but with a widening gap between top and bottom performers, highlighting the need for companies to understand their position in this trend.
Who should watch
- AI Engineers and Builders
- Product Managers
- Leaders seeking to understand AI's true impact on engineering
- Teams struggling to quantify AI ROI
- Organizations evaluating AI tool adoption
Key takeaways
- AI adoption shows a median productivity gain of approximately 10%, but a significant performance gap is emerging between early adopters and laggards.
- AI usage quality appears more critical than sheer volume; excessive token usage can even lead to a "death valley" effect where productivity decreases.
- Codebase hygiene, including tests, types, documentation, and modularity, strongly correlates with AI productivity gains, suggesting investment in code quality is essential.
- Engineers must learn when to use AI and when not to, as unchecked AI use can accelerate codebase entropy and lead to a loss of trust if outputs require heavy rewriting.
- A new AI engineering practices benchmark can quantify how teams are using AI, revealing differences in adoption and usage patterns even within the same company.
- Measuring AI ROI requires looking beyond business outcomes to engineering metrics, as direct links to revenue are often obscured by confounding variables.
- A case study revealed that while PRs increased by 14% after AI adoption, code quality decreased by 9%, rework increased significantly, and effective output remained largely unchanged, questioning the ROI based on simple metrics.
- *Metrics don't need to be flawless to be useful.*
Notable quotes
*AI usage quality matters more than AI usage value.*
*Invest in codebase hygiene to unlock these AI productivity gains.*
*Metrics don't need to be flawless to be useful.*
Unofficial community note. Prefer the recording for nuance.