Is “Not deploying on Fridays” an outdated practice?

2022-07-09  |   7 minutes

Is not to deploy on Fridays really that wise advice, that it used to be in the past? I would say "No"!
Read More
/img/import/2022-07-09-not-deploying-on-fridays-outdated-practice.jpg

Scratch the Backlog – There is a better way to plan your work

2022-06-25  |   5 minutes

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.
Read More
/img/import/2022-06-25-scratch-the-backlog.jpg

From two manual monolithic deployments a week to 15+ automated deployments a day

2022-06-11  |   13 minutes

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.
Read More
/img/import/2022-06-11-continuous-deployment-for-the-entire-organisation.jpg

DRY – DO repeat yourself

2022-04-30  |   7 minutes

DRY is one of the most misunderstood and abused principles. Copy more, reuse less!
Read More
/img/import/2022-04-30-dry-do-repeat-yourself.jpg

Code ownership conflicts as a signal for structural mismatch

2022-02-19  |   4 minutes

Code ownership on a team-level can not only help to identify the team that has knowledge in a certain area, it also can serve as a signal for a mismatch between architecture and team structures.
Read More
/img/import/2022-02-19-code-ownership-conflicts.jpg

Code Ownership: Keeping the balance between structure and agility

2022-02-12  |   5 minutes

Code ownership is an important topic when it comes to enabling your teams and allowing developers to improve the system while keeping the overhead of changes low. While today, most companies would (hopefully) agree, that individual code ownership is bad because it creates knowledge silos and makes the organisation dependent on individuals, code ownership still is essential on a larger scale.
Read More
/img/import/2022-02-12-code-ownership.jpg