Measuring developer productivity in the AI era

Software engineering at Google & CS education with Titus Winters

Topic 8 of 10

Published Oct 28, 2026 · Clip 1:01:23–1:11:43 (10:20)

Titus describes his Adobe role as a senior IC in developer experience, calling it 'the business of productivity.' He proposes an index-metric approach to measuring productivity — bundling many signals via wisdom-of-crowds trade-off games — which Adobe is partially implementing. Drawing on his develop-deploy-operate paper, he identifies four forms of impact: product success, compute efficiency, engineering capacity, and changing the game. He argues AI's value lies mostly in this fourth category, doing harder, more valuable things (like a JPEG parser in weeks), which current metrics cannot capture — illustrated by an engineer's AI-written replacement for an expensive licensed component and senior engineers' observation of more code, more outages, but unknowable feature value.