Developer Productivity Engineering is fast becoming an integral part of the development & release process in the Software Engineering world today. The benefits of investing in Productivity Engineering significantly outweigh the cost and frustration of inactivity in this space.
In this video series, we will cover the importance of productivity engineering and explore why Android developers & teams should embrace productivity engineering as part of their development lifecycle.
We will cover the following key topics:
- Tips to improve your Gradle builds by achieving faster, stable, and reproducible builds.
- Importance of Build Scans in solving build problems & improving team collaborations.
- Build Caching to significantly speed-up builds.
- Impact of Build Cache Node Replication on your builds.
- How to make a compelling, data-focused case for Productivity Engineering to your team and manager.
I will take you through a real-life example of using Gradle Enterprise to diagnose builds, improve the build experience, and make a business case for a focus on Productivity Engineering.
Gradle Enterprise is a paid service that scans every developer & CI build and provides a remote cache for unchanged builds & tests artifacts. Gradle Enterprise gives you the data and tools to shrink wasted build time by up to 90%.
Some of the key Gradle Enterprise features we will look into are:
- Build Scans and Scan Comparisons - Gaining access to Root Cause Analysis Data.
- Trends and Insights - Enables you to Practice Continuous Learning & Improvement.
- Build Cache & Distributed Testing - To Reduce Build & Test Times Up to 90%.
- Failure Analytics - Eliminate Flaky Tests and Other Avoidable Failures.
- CI Build Cache & Resource Profiling - To Optimize CI Cost & Resource Efficiency.
We'll cover important build optimization properties and walkthrough several plugins to help diagnose and fix build issues.
Lastly, we will highlight the value proposition of Gradle Enterprise and other open-source tools to make data-driven decisions to continuously improve your build process and developer productivity.
My goal for you is to gain a better understanding and appreciation for Productivity Engineering.
If there's anything specific I haven't mentioned above that you would like me to cover, feel free to mention it in the comments section below.
Thanks again to Nate Ebel for reviewing an early draft.