Sign in Subscribe

Software Architecture

When trade-offs, debt and legacy collide

When trade-offs, debt and legacy collide

Every architectural decision has a cost. Some costs are accepted, some are postponed, and some appear because evolution never happened. Understanding these differences can change how you assess and improve a system.

Domain Types: What if you build nothing? (Part 3)

Domain Types: What if you build nothing? (Part 3)

Every architectural decision comes with a cost. Sometimes the most pragmatic solution is not another service, application, or vendor, but a simple manual process.

AI writes code, architecture and tests keep it sane

AI writes code, architecture and tests keep it sane

AI can generate code faster than ever, but code alone does not guarantee quality. Without well-defined architecture and meaningful tests, you lose control over what is being built and whether it actually works.

Keep it together or split it? Making boundary decisions under uncertainty

Keep it together or split it? Making boundary decisions under uncertainty

You’ve explored the domain and defined boundaries - but what if you’re still not sure where to draw the line? Learn how to decide whether to keep responsibilities together or split them when uncertainty is unavoidable.

Ambivalent feelings about details in domain modeling

Ambivalent feelings about details in domain modeling

More detail doesn’t always mean better understanding. In domain modeling, too much creates noise, too little creates risk. The real challenge is deciding what truly matters - and accepting that detail is always a decision.

Knowledge reveals complexity - and improves Architecture

Knowledge reveals complexity - and improves Architecture

The more you understand the domain, the harder decisions become. That’s not a problem - it’s a signal. Architecture is not about simplifying reality, but about navigating its complexity and making better decisions despite uncertainty.

Software Architecture must evolve - or it becomes the Problem

Software Architecture must evolve - or it becomes the Problem

Architecture is often treated as something written in stone. In reality, software continuously changes - and architecture must evolve with it. The real danger isn’t changing architectural decisions. The danger is when they never change at all.