Is not to deploy on Fridays really that wise advice, that it used to be in the past? I would say "No"!

Long backlogs do not give you the overview and clarity you hope for. Instead they lead to false hopes and set you up for disappointment and wasted time.

We did it. Roughly two years after I joined BRYTER and one year after we started the developer experience team, we finally ended the era of manual deployments for roughly 15 teams.

Developer experience engineering is a pretty new discipline. However, there are numerous parallels to user experience engineering. Therefore, DX engineers can learn from the teachings of UX engineering.

DRY is one of the most misunderstood and abused principles. Copy more, reuse less!

As a developer experience team, we are often working in a platform mode but are constantly shifting into enabling mode for better results.

Once you have decided, that a developer experience team would provide value to your organisation, the question is, how such a team should be set up, how it should be shaped, and how it should interact with other teams.

Great developer experience is directly linked to great developer productivity and an important factor for company success. This article starts to answer the question how great developer experience can be achieved.

Companies might fall into the trap to believe that developer experience is a nice-to-have luxury rather than a necessity. However, this is not the case. High developer productivity results from a great developer experience and thus, the companies' success ultimately relies on this.

When talking about developer experience, there are a couple of other names thrown into the conversation that all kind-of mean the same, but IMHO have a slightly different touch / focus and can be perceived quite differently.