Developer Productivity Engineering: What's in it for me?
summary
Developer Productivity Engineering shows concrete wins: using Gradle DevVelocity with remote build caching cuts builds (Spring Boot example 20→3 minutes), test distribution reduces CI cycles (Netflix 62→5 minutes), and ML predictive test selection runs ~30% of tests for given changes. Case studies: 11-dev team with 4‑minute builds vs 6‑dev team with 1‑minute builds yields far more weekly builds. Tools cited: build scans for debugging flaky tests, automated flaky detection, observability on developer environments; reported outcome is higher throughput and an 84% uplift in developer happiness.
AI-written summary · about
chapters (17)
- 0:00The reality of developers
- 1:34What defines productivity
- 2:53The myth of the 10x engineer
- 5:55What is DPE?
- 7:37Pain points in development
- 9:39Fast feedback strategies
- 12:55Build caching technology
- 15:06Remote build caches
- 16:00Test distribution and AI
- 19:08Acceleration technology impact
- 20:30Troubleshooting broken builds
- 22:17Flaky test problems
- 24:19Identifying flaky tests
- 26:43Observability and metrics
- 28:11Treating dev as production
- 30:20In Summary
- 34:19Conclusion
related talks
44mDeveloper Productivity Engineering: What's in it for Java Developers?
45mDeveloper Productivity Engineering – The Next Big Thing in Software Development
54mDeveloper Productivity Engineering Deep Dive
40mDeveloper Productivity Engineering for Open-Source Communities
43mDeveloper Productivity Engineering – The Next Big Thing in SW Development
02h 31mDeveloper Productivity Engineering - Extended Session
27mDeveloper Experience: It’s Time to Start Complaining
19mAvoiding work is work - but it pays off!