Surviving the Techpocalypse with Developer Productivity Engineering
summary
Half a million tech layoffs in three years set the stage for a push to measure and speed developer feedback: using Developer Productivity Engineering with concrete tactics—incremental builds, remote build cache (20 minutes saved in one demo), testcontainers for local integration tests, Sonar/quality gates, and predictive test selection (Meta-style ML that saved an org 61 days of build time and predicts tests with 98.7% accuracy). Claims include an overall productivity and developer-joy lift of ~81–84%, a 12× local build speedup from parallelization, and cloud fan-out for running tests in parallel.
AI-written summary · about
chapters (7)
- 0:00Introduction and tech layoffs
- 13:26Survivor syndrome and morale
- 23:56Developer motivation and autonomy
- 27:13Engineering better productivity
- 37:10Speeding up builds and tests
- 48:40Measuring and improving DPE
- 51:08Summary and call to action
related talks
02h 31mDeveloper Productivity Engineering - Extended Session
45mDeveloper Productivity Engineering – The Next Big Thing in Software Development
36mDeveloper Productivity Engineering: What's in it for me?
44mDeveloper Productivity Engineering: What's in it for Java Developers?
43mDeveloper Productivity Engineering – The Next Big Thing in SW Development
54mDeveloper Productivity Engineering Deep Dive
27mDeveloper Experience: It’s Time to Start Complaining
43mMeasuring Developer Productivity: The Good, the Bad and the Data