Developer productivity is a crucial topic for high-performing software organizations. It becomes even more important when times get tough and the budgets are small.
Mapping the architecture of the system that you are building in your company, is a worthwhile activity. With a bit of preparation you can run successful architecture workshops in a remote setup.
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.
Subscribe to our newsletter and never miss an update.
No spam. Take my word for it!
Get notified about new articles
