Developer Productivity Engineering Blog

As developers, we understand the value of data. We collect it on the performance of our applications, use it to find out how our users are behaving and how to improve their experiences, and monitor our apps to anticipate problems before they strike. However, we’re often living in a data vacuum when it comes to things that impact developer productivity and the overall experience. You need data to show what is introducing friction and toil into your job. You need data to show the risks that exist from using outdated tools. And you need data to show that your solutions can fix these issues.

Criteo (NASDAQ: CRTO) is a publicly-traded online advertising provider valued at over $2 billion and headquartered in Paris, France. Its industry leading Commerce Media Platform connects thousands of marketers and media owners to deliver richer consumer experiences from product discovery to purchase.

Criteo (NASDAQ: CRTO) est un fournisseur de publicité en ligne coté en bourse évalué à plus de 2 milliards de dollars et dont le siège est à Paris. Sa plateforme Commerce Media, leader du secteur, connecte des milliers de spécialistes du marketing et de propriétaires de médias pour offrir aux consommateurs des expériences plus riches, de la découverte du produit à l’achat.

This post describes how to make the Quarkus build goal cacheable with minimal modifications to the Maven build configuration, reusing outputs from previous builds to save time.

Holly Cummins from Red Hat speaks about their journey of using Develocity to accelerate Quarkus builds, whether developer productivity and developer joy are opposites, and how helpful AI is for developers.

How often do build performance regressions happen and what’s the impact on developer productivity? The Netflix Android team says these regressions can happen often and sometimes significantly impact CI and local developer machine build times. Fortunately, Develocity’s Build Validations Scripts and quick investigation Build Scan® links can help you identify build cache misses, measure the impact, and prioritize the fix. Find out how Netflix uses Develocity to efficiently monitor build performance at scale and how you can too.

Dealing with dependencies is an inevitable part of developing Java applications with any build tool, and Apache Maven is no exception. As your project grows, the complexity of managing these dependencies can lead to the dreaded “dependency hell,” where conflicts, version mismatches, and unresolvable libraries disrupt your build. In this post, we’ll explore five strategic approaches for managing dependencies effectively in Maven.

The more quality matters to an organization, and the more tests they have, the more likely it is that some of these tests will be “flaky”. During one DevProdEng Showdown, we asked DevProd experts at four large financial organizations about how they address flaky tests. They agreed that the most effective way to address flakiness in a test suite is “a combination of mechanisms and mindset change.” Find out why these top banks invest in a developer culture that addresses flaky tests. 

We’re excited to announce a new capability for Develocity called Reporting and Visualization. The data that Develocity collects and collates is so valuable for providing insights into developer team productivity that we thought it essential to make it even easier to access, understand, and query. While it uses a familiar toolchain for querying and reporting the local and CI build data available in Develocity, the data is then fed into Grafana, so you can use the full power of a tool designed for visualizing and understanding data.

A build cache is one of the most effective tools for boosting productivity by reducing build times and shortening feedback cycles. However, many developers are unaware of what a build cache is and how it can help. This blog post will introduce you to a build cache and then walk you through using a build cache for Apache Maven projects.