What's changing
Engineering is in the middle of its sharpest productivity shift since the move to the cloud. AI-assisted authoring, autonomous agents, and code-generation tooling are compounding inside review and merge, and the teams that picked them up first are not waiting for the rest. Output per engineer at the top is pulling away from the median fast enough that the gap reshuffles week to week.
How we benchmark it
ETV / dev / month
Engineering Throughput Value scores every merged commit by the depth of work it represents (Growth, Maintenance, Fixes), then averages it per active contributor and normalizes to a 30-day calendar month using a 90-day moving window.
AI share of code
The fraction of merged code attributable to AI-augmented authoring, aggregated quarterly from public commit metadata.
Forecast
A damped extrapolation of the rolling 90-day per-month trend forward one year, with a confidence cone that widens further from today.
Why speed is the benchmark
Engineering isn't just speed. It's building the right thing. But the minimum speed required to build the right thing keeps rising, because the teams that iterate fastest learn fastest. You're much more likely to ship something users actually want when you can take twenty shots at it instead of two.
Read the full methodology →