Developer Productivity Engineering: What's in it for Java Developers?
summary
Developer productivity engineering focuses on practical fixes: enable local and remote build cache (Spring Boot sees 63% build time saved), add predictive test selection to run only likely-relevant tests, distribute tests across cloud agents to cut long test phases, and ship build scans for monitoring flaky tests and environment drift. Examples include Gradle and Maven cache extensions, DevVelocity integrations, CI fan-out vs aggregated test distribution, and a Dell case claiming ~41 developer-days saved equivalent over a week.
AI-written summary · about
chapters (14)
- 0:00Introduction to talk
- 1:25Developer frustrations today
- 6:40What is Developer Productivity Engineering
- 12:33Key DPE principles
- 17:47DPE vs DevOps evolution
- 23:01Four ways to speed up builds
- 24:26Build caching explained
- 28:01Reproducible builds benefits
- 29:24Predictive test selection
- 32:34Test distribution techniques
- 35:23Monitoring builds with scans
- 39:16Handling flaky tests
- 41:02Tools and time management tips
- 42:29Conclusion and resources
related talks
36mDeveloper Productivity Engineering: What's in it for me?
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
02h 31mDeveloper Productivity Engineering - Extended Session
40mDeveloper Productivity Engineering for Open-Source Communities
19mAvoiding work is work - but it pays off!
27mDeveloper Experience: It’s Time to Start Complaining