#Practices

Maintaining amble of focus and deep work time as an individual is a critical precondition of being part of a high-performing team. In this article I will give seven tips on how to get more deep work time throughout your week.

Unlock the potential of your developer team with remote work! Discover the key benefits of working from home, including increased productivity, better work-life balance, and improved collaboration. Learn how remote work can help your team work more efficiently and effectively, and create a more flexible, fulfilling work environment. Read on to learn more!

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.

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.

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.