Developer Productivity Engineering - Extended Session
summary
Claims that developer productivity improves by fixing feedback-cycle bottlenecks with concrete tools and metrics, not pep talks: build caching (local + remote) cuts clean build time from minutes to seconds, returning “44 engineering days” per year for a six‑person team and 5,200 days for a 100‑person team; test distribution plus predictive test selection shrinks a 62‑minute test run to under five minutes at Netflix and avoids tens of thousands of pointless tests for Micronaut; build scans capture failures, flakiness and root cause data so problems get fixed instead of rerun.
AI-written summary · about
chapters (8)
- 0:00Introduction to DPE
- 10:09Developer productivity crisis
- 25:18Theory of constraints in software
- 1:00:25Build acceleration technologies
- 1:35:24Inefficient troubleshooting
- 2:02:27Flaky tests and avoidable failures
- 2:17:57CI impact and optimization
- 2:31:08Q&A and resources
related talks
45mDeveloper Productivity Engineering – The Next Big Thing in Software Development
36mDeveloper Productivity Engineering: What's in it for me?
54mDeveloper Productivity Engineering Deep Dive
52mSurviving the Techpocalypse with Developer Productivity Engineering
44mDeveloper Productivity Engineering: What's in it for Java Developers?
43mDeveloper Productivity Engineering – The Next Big Thing in SW Development
27mDeveloper Experience: It’s Time to Start Complaining
46mDeveloper Productivity at Scale