Sign in Subscribe

Sebastian Malaca

Sebastian Malaca

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.

Link Dump #232

Link Dump #232

Did you already read something interesting this week? If not, here's an opportunity to change it.

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.

Mind the Architecture

After 15 years of writing and 473 articles, I decided it was time for an evolution. Not a restart, but a new place to share ideas about building software and architecture that can evolve with changing business needs.

Link Dump #231

Link Dump #231

Change is the only constant in life. Even so, I will do the best to help you make reading your other constant :)

Domain Types: Build, buy, or outsource?

Domain Types: Build, buy, or outsource?

Architectural decisions evolve with knowledge. Domain classification provides direction, helping teams balance building, buying, and outsourcing as the system and market change.