Developer productivity is waste
summary
Argues that measuring developer productivity is mostly misleading and instead improving the outer loop — reliable release pipelines and automation — moves outcomes; cites DORA/SPACE frameworks, a Pivotal Labs–style survey and CD Foundation data showing CI/CD adoption is flat and only about 29% report full automation (so ~70% still don’t automate builds/tests). Recommends building repeatable CI/CD pipelines, standardizing platforms (fewer than four) and tracking developer satisfaction as a proxy for impact.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:30Developer productivity metrics struggle
- 3:58Who asks about productivity
- 5:44Outer loop of development
- 12:46Defining developer productivity
- 15:57Developer productivity frameworks
- 18:22Measuring developer experience
- 20:49CI/CD pipelines importance
- 23:37CI/CD adoption stagnation
- 26:01Platforms and developer productivity
- 27:45Reducing platform fragmentation
- 29:53Developer productivity resources
related talks
51mDeveloper productivity is waste
43mMeasuring Developer Productivity: The Good, the Bad and the Data
34mBuilding a Culture For Developer Productivity
43mThe Past, Present and Future of Developer Productivity Theories and Metrics
27mDevelopers Expose What's Breaking Productivity in Their Companies
33mBeyond developer productivity: what's next?
24mBeyond the Commit: A Fireside Chat on AI and Developer Productivity
02h 31mDeveloper Productivity Engineering - Extended Session