Measuring Developer Experience in the Age of AI
summary
Argues that AI adoption is not the same as productivity and urges concrete measurement: DORA data shows job satisfaction and documentation quality rising and code complexity falling, yet software delivery performance (throughput and stability) drops as AI adoption increases. Recommends baselining, small controlled changes, integrating tools into measurement frameworks, tracking signals like code acceptance rate and PR cycle time, surfacing qualitative developer feedback, defining purpose-driven use cases, and using metrics to guide learning not punish teams.
AI-written summary · about
chapters (16)
- 0:00Measuring dev experience with AI
- 1:26Redefining dev productivity
- 3:11AI adoption vs productivity gains
- 6:01Dev experience and AI impact
- 7:24Balancing human-centered AI
- 9:09Connecting AI tools to business
- 11:18Measuring AI ROI through dev experience
- 13:47Purpose-driven AI adoption
- 14:28Unexpected metrics in AI dev experience
- 16:37Dev engagement with AI tools
- 19:26Measuring creativity in AI workflows
- 21:10North stars for AI improvement
- 24:21Richer dev data reshapes leadership
- 26:51Metrics for continuous improvement
- 27:56Data deepens empathy in teams
- 31:11Closing reflections on AI and metrics
related talks
45mDeveloper experience in the AI era
28mAI as an Amplifier: State of AI assisted Software Development
43mMeasuring Developer Productivity: The Good, the Bad and the Data
46mMeasuring the Impact of AI on Developer Productivity
56mAI as an Amplifier: State of AI-Assisted Software Development
24mBeyond the Commit: A Fireside Chat on AI and Developer Productivity
18mHumans + AI: The Future of Software Development Teams
46mMaking AI Adoption Work: A Practical Structure for Modern Software Development