Developer Experience: It’s Time to Start Complaining
summary
Claims that developer productivity engineering reduces toil by measuring and fixing concrete bottlenecks: teams find local build times often nea rly invisible until measured and discover worst cases like 20‑hour feedback cycles. Gradle outlines three acceleration tools — a caching solution, distributed elastic unit test execution, and predicted test selection (Google/Facebook research) — and recommends dashboards for flaky tests and aggregated failure impact. Also ties supply‑chain fixes (Sigstore-style signing) to avoiding all‑hands vulnerability churn.
AI-written summary · about
chapters (6)
- 0:00Intro
- 2:34What is Developer Productivity Engineering?
- 6:55Creative vs destructive flow
- 15:04Metrics and visibility
- 21:19Open source supply chain security
- 22:39Blockchain, AR & VR
related talks
36mDeveloper Productivity Engineering: What's in it for me?
02h 31mDeveloper Productivity Engineering - Extended Session
45mDeveloper Productivity Engineering – The Next Big Thing in Software Development
19mAvoiding work is work - but it pays off!
44mDeveloper Productivity Engineering: What's in it for Java Developers?
30mAndroid Developer Productivity
47mHow to win in software development with tighter feedback loops
43mDeveloper Productivity Engineering – The Next Big Thing in SW Development