Architecture that compounds,
not drags you down.
I write about platform decisions that pay dividends over years, and the invisible costs that accumulate when we get them wrong.
Three ideas that change how
you think about platforms.
Compounding Architecture
Most architecture decisions are treated as one-time costs. But the best ones compound. Clean domain boundaries make the next feature faster. Good abstractions make onboarding shorter. Solid testing makes AI tools more effective. Compounding Architecture is the goal: patterns and decisions that build on each other and pay dividends over time. The opposite of "move fast and break things", move deliberately and build momentum.
Tech Drag
Tech Drag is the continuous, invisible cost of poor patterns. It grows as you try to move faster. Every shortcut that "saves time" adds friction to every future change. Past 50 engineers, coordination overhead grows geometrically. AI amplifies whatever is already there. Clean codebases get exponentially more value while high-debt codebases get worse. Tech Drag is the enemy. And most teams can feel it long before they can measure it.
The People Side
In an era where AI handles more and more of the code, engineering becomes about system design and helping people adapt to that new reality. The most expensive architecture decisions are not the wrong ones, they are the ones nobody realised they were making. Conway's Law is not optional. Technical decisions are organisational decisions. The teams that thrive will be the ones that never forget the human dimension.
25 years of seeing what
breaks and what lasts.
I'm Dariusz Sadowski. I've spent 25 years building and scaling software platforms, 10 of those in fintech and banking, where the architecture has to work or the money doesn't move.
I've inherited the 5,000-line God objects. I've watched sharp engineers burn out because the platform fought them on every commit. I've seen the same architectural mistakes play out across companies and industries. The patterns are predictable, which means they are preventable.
Today I write about the intersection of architecture and leadership. How technical decisions are organisational decisions. How AI is reshaping what it means to be an engineer. And how the fundamentals, clean boundaries, good tests, clear documentation, still beat tools, every time.
—Pattern recognition from 25 years of building. Not a framework. Not a methodology. Just what I've seen work.
Think in systems.
Build what compounds.
Every edition of The Modern Architect covers one architecture decision in depth, the trade-offs, the human factors, and the patterns that pay dividends. Join technical leaders who think beyond the code.