#Software-Craft

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!

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.

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.

Blameless post-mortems are an effective tool to facilitate learning from failures, to share knowledge and to significantly improve the entire system, including software, infrastructure, and processes.

Keeping people 100% busy will prevent them from innovating and improving. Therefore, teams should have slack that enables the to learn, adapt and improve.

If you do not test in production, your customers are the only ones, who do. While it sounds scary at first, testing in production is an important addition to pre-production quality assurance processes.

When moving towards a more continuous software delivery process, focus on evolving the culture instead of just automating the processes.

Decoupling deployments and releases gives you a better control about when system changes are made available to users and can help you to avoid complicated rollback processes in case, things go wrong.

Walls in your deployment process block value-flow and slow-down feedback cycles. Here is how you can detect and remove them.