Embracing Productivity Engineering in Android
summary
A concrete case study showing a trial install on GCP of Gradle Enterprise with build scans, the Gradle Doctor plugin, local and remote build cache plus cache node replication that cuts PR build times from ~30–40 minutes to about 8–9 minutes and shrinks one 18-minute task to 17 seconds. The team captures baseline data, reintroduces caching, fixes JVM and task misconfigurations, migrates CI to GitHub Actions, and uses scan comparisons to prove cost savings and make a data-driven business case.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 7:27What is productivity engineering
- 11:40Premise’s productivity challenges
- 14:55Gradle Enterprise trial and setup
- 25:13Tips and tools to improve builds
- 33:25Final takeaways and Q&A
related talks
45mDeveloper Productivity Engineering – The Next Big Thing in Software Development
43mDeveloper Productivity Engineering – The Next Big Thing in SW Development
44mDeveloper Productivity Engineering: What's in it for Java Developers?
36mDeveloper Productivity Engineering: What's in it for me?
02h 31mDeveloper Productivity Engineering - Extended Session
01mIncrease Your Productivity with Tools
54mDeveloper Productivity Engineering Deep Dive
27mDeveloper Experience: It’s Time to Start Complaining