#Technical-Leadership

BRYTER, a German LegalTech company, improved how they update their software by moving to continuous deployments. This change allowed them to make updates faster, improve their software quality, and give their teams more control and understanding of the process. As a result, they saw fewer problems and could fix issues quicker.

Organizations often accumulate technical debt as the pressure to deliver customer value quickly increases, systems grow, and extending functionality the *right* way becomes more difficult.

The Inverse Conway Manoeuvre is unlikely to work in existing sociotechnical systems of a certain size and stability. It is even less likely to work in remote companies and distributed teams.

Teams can have dysfunctional behaviours while everything looks good on first sight and there seems to be harmony. Here are 5 signs that there might be an issue that hinders the team to excel.

Investing in developer experience leads to improved productivity, better engineering practices, and increased stakeholder satisfaction. Positive developer experience starts with providing access to technology and tools, fostering collaboration, and streamlining workflows. Create a comfortable work environment, offer training opportunities, and invest in your team's growth to achieve a motivated and productive development team.

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.

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.

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.

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.