Breeding 10x Developers with Developer Productivity Engineering
summary
Claims that 10x engineers are mythical but 10x organizations are real backed by the Coding Wars finding of ~10:1 top to bottom developers and an ~11x gap between organizations, with within-company variance only ~20%. Concrete fixes include build cache (Gradle, Maven GA) cutting build/test times 40–90%, test distribution on Kubernetes (Netflix 62m → <5m), predictive test selection and ML, and build scans for failure analytics. DPE teams centralize these practices, and 80% of adopters say it makes work more enjoyable.
AI-written summary · about
chapters (19)
- 0:00Introduction and welcome
- 1:26Origin of the 10x developer myth
- 3:52Productivity within vs between organizations
- 6:00Manufacturing 10x organizations
- 7:26SPACE framework explained
- 9:12Developer experience bottlenecks
- 10:14Developer flow and brain science
- 11:58Developer calendar reality
- 13:26Developer experience friction
- 14:51Why feedback cycles matter
- 16:15Cognitive fatigue and innovation
- 17:16Build caching basics
- 18:42How build caching works
- 20:06Remote caching and test distribution
- 21:10Predictive test selection
- 22:14Build scans for troubleshooting
- 22:58Tracking local build times
- 23:39DPE analytics and joy
- 24:42Next steps for DPE adoption
related talks
43mDeveloper Productivity Engineering – The Next Big Thing in SW Development
45mDeveloper Productivity Engineering – The Next Big Thing in Software Development
54mDeveloper Productivity Engineering Deep Dive
35m"DevOps Reframed: Embracing the Path to Developer Productivity Engineering"
02h 31mDeveloper Productivity Engineering - Extended Session
52mSurviving the Techpocalypse with Developer Productivity Engineering
36mDeveloper Productivity Engineering: What's in it for me?
10mAchieving engineering velocity by optimising developer experience