Android Developer Productivity
summary
Claims that slow builds are measurable tech debt with a concrete example: 60 wasted seconds × 50 builds × 50 devs → 42 hours lost per day. Shows five build validation scripts that reproduce and capture outputs to diagnose up-to-date and cache misses (incremental, local cache, relocatability, CI→CI, CI→local). Demonstrates automated runs via a GitHub Action, a new Gradle Enterprise API for listing builds, cache performance and attributes, and queries that rank slowest projects/users and surface negative avoidance savings and cache failures. Mentions Room path issues and a project-summary utility.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:31Slow builds as tech debt
- 3:16Gradle Enterprise overview
- 5:45What is build caching
- 6:27Build validation scripts
- 13:07Script command line usage
- 16:00Automating with GitHub Actions
- 17:05New Gradle Enterprise API
- 18:53API use cases examples
- 21:23Finding slowest projects
- 22:31Ranking teammates by build time
- 23:54Negative avoidance savings tasks
- 25:41Build cache error analysis
- 26:43Project summary tool
- 27:27New Android features in Gradle Enterprise
- 28:51Room path sensitivity issue
- 29:11Resources and closing
related talks
41mKeeping your team's Gradle builds in top shape
33mKeeping your Gradle builds in top shape
37mBecoming and Staying a Productive Developer with Build Scans, Build Validation Scripts and Gradle
27mDeveloper Experience: It’s Time to Start Complaining
36mDeveloper Productivity Engineering: What's in it for me?
33mIMPROVING ANDROID BUILD PERFORMANCE
36mKeeping your team’s Gradle builds in top shape
36mImproving Gradle Builds