GitHub - architecture-decision-record/architecture-decision-record: Architecture decision record (ADR) examples for software planning, IT leadership, and template documentation

An intentionally quiet and unassuming (and empty) blog

Developer Relations has gone through quite a few changes over the last few years. In that vein, some people have found new skills in the ever-evolving world of tech. Along their journey, they moved away from DevRel, but still use those abilities in new ways. So, what is it like when you bounce from DevRel?

One of the key roles of the leadership team in the company is to make clear decisions1 and unlock decision making internal link on other organizational levels. Topics are frequently complex and need data and intricate relationships among them to describe the problem-space. Yet, many leadership teams are using presentations2 to synchronize teams and describe the problem.

My thoughts on the blog post 'How to be a -10x engineer', which was quite popular in Hacker News.

Transform code review from critique to collaboration. Learn effective feedback techniques that enhance code quality and boost team morale. Transform code review from critique to collaboration. Learn effective feedback techniques that enhance code quality and boost team morale.

The business is growing, and your engineering team is too. Great news - until the sprawl sets in. How can your teams and processes scale with consistency and maturity?

To efficiently develop software, it is crucial to control its quality, particularly the architecture and code structure. In Java, ArchUnit, a library for testing certain aspects of architecture and design, can help. In this article, I’ll present ten practical ArchUnit tests based on my experiences with developing a Spring Framework-based application.

If issues, pull requests, and project boards are the best way to develop software, should they not also be the best way to manage software development?

My not-a-professional website

68 comments