The Agile Software Architect Debate: How Do Architects Add Value?
A personal look at how agile software architects add value today through platform engineering, Team Topologies, and better developer experience.
Software architecture in practice
Blog of aharchitect
In my blog I share my key learnings, discuss about the role and its contribution to development and, of course, examine related topics like domain-driven design, quality-driven design and more.
Start here
The Agile Software Architect Debate: How Do Architects Add Value?
A personal look at how agile software architects add value today through platform engineering, Team Topologies, and better developer experience.
Latest Post
Second attempt at zero feed-in: making my solar system more stable
How I improved the zero feed-in control of my solar system after delayed meter and battery readings made the first version less effective.
Find the right topic quickly
About this blog
Software Architecture is a Socio-Technical Discipline
I work at the intersection of software architecture, domain design and organizational structure. My focus is on understanding complex systems, shaping meaningful boundaries and creating the conditions in which teams and software can evolve effectively.
I believe good architecture creates clarity without centralizing decisions. It reduces unnecessary dependencies, makes responsibilities and trade-offs visible and enables teams to make sound decisions autonomously while maintaining coherence across the larger system.
Architecture is therefore an enabling discipline for me. It creates shared understanding and provides the platforms, guardrails and decision structures that help teams succeed.
Domain-Driven Design, Quality-Driven Design, collaborative modelling, architecture fitness functions and platform engineering are tools I use depending on the problem and context. They are not goals in themselves.
Designing boundaries and conditions that help teams and software evolve.
About me
My perspective on architecture has been shaped by almost two decades of working with very different systems, domains and organizations — from industrial automation and medical software to enterprise platforms and cloud-native systems.
That breadth is an important part of how I approach architecture today.
More about my background and experience → here
The contents on this website reflect exclusively my opinion, not that of my current or past employers!
Latest posts
Recent architecture posts
The Agile Software Architect Debate: Do We Need Architects?
Exploring whether agile teams need dedicated software architects. Analysis of team models, experience levels, and project scales with practical guidance for modern development teams.
Bounded Context Definition: Why the Common View Is Insufficient
The bounded context definition encompasses more than linguistic boundaries. Learn the essential facets teams need for successful software development.