Developer Productivity Engineering Blog

Like many companies, the software development experience at Elastic was starting to become negatively impacted under the increasing strain of slowing builds and inefficient process for testing and debugging. And, the pain was only expected to increase in line with the growth of development teams, code bases, and repositories. The cost of inaction was projected to soon become unbearable.

In this webcast, Mark Vieira, Senior Software Engineer at Elastic discusses with Gradle, Inc. CEO, Hans Dockter, how Elastic overcame the natural resistance to change their process and toolset by quantifying the Cost of Inaction and blazing a new path toward build engineering excellence.

Gradle 6.0 is the culmination of several years of innovative improvements in Dependency Management. Embracing the idea that there is more to software composition and reuse than just putting a set of jar files on the classpath, Gradle now offers a new metadata format to richly define software components that are often made up of multiple files, different variants and specific constraints on their dependencies.

Whether producing private or public components, most projects are built with multiple software libraries interacting together. Aside from knowing what to publish and how to do so, this webcast covers strategies for streamlining the publication and integration processes.

In this webinar, Hans Dockter, CEO & Founder of Gradle, talked about the emerging practice of developer productivity engineering, a discipline of using data to improve essential development processes from build/test to CI/CD.

How can you use data visualizations with your build data to improve the reliability and performance of your build?

How do we create a fast and reliable reliable CI process and pipeline using the tools that we built ourselves?In this recorded webcast, Gradle Enterprise team leads…

As your project grows larger and more complex, its build becomes slower if left unchecked. But recent Gradle releases give you new capabilities to improve your Java and Android build speed.

How does LinkedIn create a culture of developer productivity that is capable of building over 100,000 times a day?

In this document, I want to provide a model on how to calculate the costs of your builds and the return you get on improving it.

The role of the build engineer is undergoing a transformation. Build engineers are becoming the key to success for any software producing company. But this transition is not happening without a lot of pain.