Developer Productivity at Scale: Using data and acceleration techniques to improve essential processes

“Software is eating the world” means all innovations in the company must be channeled through software. As Architects, we create the choices, trade-offs and conditions for software-based innovation to occur successfully. Those choices also affect how software is built and tested and vice versa. For example proper modularization does not just improve maintainability and separation of concerns, but can also dramatically impact the time it takes to build and test software. , Mapping micro-services to source repositories is often influenced by build and test time constraints, with often suboptimal results.

Good architecture and developer productivity engineering should work hand-in-hand.

The paradox of a successful software team is that as the codebase and team sizes grow - it becomes harder to maintain the automation, fast feedback cycles, and reliable feedback that enables the software development team to execute at their full potential including sticking to the architectural roadmap. Compared to other industries, the software development process is in the dark ages, with little data to observe and optimize the process itself.

Join Hans Dockter, founder and CEO of Gradle for a discussion of how to measure the impact, and apply data and acceleration technologies to speed up and improve the essential software development processes from builds to testing to CI and how this will benefit and enable better architecture.