Becoming and Staying a Productive Developer with Build Scans, Build Validation Scripts and Gradle
summary
Shows concrete tooling and fixes for Gradle-based Android builds: use the DevVelocity/Gradle plugin and artifact transforms in build scans to see previously invisible work, use task inputs comparison to find cache misses caused by absolute paths, timestamps, KSP or Live Literals, and run open‑source build validation scripts that execute a build twice and fail CI on regressions. Gives numbers: 60s waste ×50 builds ×50 devs = ~42 hours/day (~10%), Spring Boot drops from 75 to 18 minutes, and fixes landed (KSP upgrade, Room Gradle plugin).
AI-written summary · about
chapters (8)
- 0:00Introduction to productivity
- 3:39Developer productivity engineering
- 7:13Insights from build scans
- 11:30Understanding build caching
- 23:23Build caching verification
- 29:01Automating cache validation
- 32:31Measuring improvement impact
- 36:27Q&A and resources
related talks
41mKeeping your team's Gradle builds in top shape
30mAndroid Developer Productivity
40mDeveloper Productivity Engineering for Open-Source Communities
36mImproving Android Developer Experience with Gradle Build Scans
33mKeeping your Gradle builds in top shape
36mDeveloper Productivity Engineering: What's in it for me?
36mImproving Gradle Builds
30mImproving Android Build performance