Developer Productivity Engineering Blog

This is a cautionary tale about the consequences of not investing enough in Developer Experience, what to do about it if you find yourself having to address those consequences, and how to avoid getting into this situation in the first place.

In a recent Inc. Magazine article, “Google Has a Productivity Problem That Has Stumped Managers for 113 Years. Will Sundar Pichai Be the First to Solve It?” (Aug. 2022), Pichai said the tech giant’s productivity levels do not match its growing headcount. Google executives have reportedly said they want to “get better results faster” with the people they have, and employees have been warned to boost performance or “there will be blood on the streets.”

For decades, the success formula for many (if not all) breakthrough business and technology productivity methodologies has been “Productivity = Speed * Efficiency”, where “efficiency” in this case refers to the ability to maintain or even improve quality as process and workflow execution speed up.

If some of the most important open source projects in the world are any indication, Develocity is quickly emerging as a staple for build and test data analytics and as a source of acceleration technology for both Gradle and Maven-based builds. Spring, JetBrains (Kotlin), JUnit, and not surprisingly, Gradle Build Tool, all rely on Develocity to improve build and test feedback cycle times and make troubleshooting more efficient with root cause analysis data (Build Scans) and failure analytics. Here’s a brief summary of the role Develocity is playing in each project and some high-level results.

There are two primary—and complementary—approaches to improving developer productivity. Both aim to use resources more efficiently and help ship code faster, while improving the developer experience.

In Santa Clara County, CA there are currently 11,000 job openings for build engineers listed on ZipRecruiter. The median annual base salary is $129,000. Why are build engineers in high demand?

For most organizations, developer productivity engineering should no longer be viewed as an informal, reactive, and opportunistic job to be done by developers in their spare time. Here are the top 3 reasons why many high-profile dev organizations have long ago established dedicated DPE teams. 

The Most Important Development in Software Engineering Since the Introduction Agile, Lean Software Development, and DevOps methodologies and Tools.

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.