Developer Productivity Engineering – The Next Big Thing in SW Development
summary
Argues that Developer Productivity Engineering (DPE) uses data and tool-driven fixes—build scans, build caching, predictive test selection, test distribution—to cut feedback time and wasted runs. Shows Maven/Gradle integrations and Gradle Enterprise-style tooling, cites LinkedIn saving ~800 hours per day via caching, Spring projects saving ~75 minutes per build, Jetty dropping 51→15 minutes with test distribution. Claims measurable ROI: faster builds mean fewer context switches, smaller change sets, and real engineering time reclaimed.
AI-written summary · about
chapters (11)
- 0:00Start
- 15:18Build Scan
- 18:19Faster Feedback Cycles
- 21:25Ci Resources
- 23:39Build Caching
- 24:00Dependency Cache
- 27:05Example from Spring Boot
- 31:54Test Distribution
- 34:34Failure Analytics
- 35:54Flaky Tests
- 39:03Make Your Software Stable
related talks
44mDeveloper Productivity Engineering: What's in it for Java Developers?
54mDeveloper Productivity Engineering Deep Dive
45mDeveloper Productivity Engineering – The Next Big Thing in Software Development
36mDeveloper Productivity Engineering: What's in it for me?
35m"DevOps Reframed: Embracing the Path to Developer Productivity Engineering"
02h 31mDeveloper Productivity Engineering - Extended Session
11mDeveloper Productivity Engineering
52mSurviving the Techpocalypse with Developer Productivity Engineering