Blogs
What shipping taught me
- Domain-Driven Design
- Architecture
Core Domain vs. Supporting Domain vs. Generic Domain
Not every part of a system deserves the same attention. Domain-Driven Design splits work into Core, Supporting, and Generic domains so you invest effort where it creates advantage.
Read article →- Domain-Driven Design
- Domain Modeling
The Hidden Cost of Bad Models in Software Design
A domain model is the software's understanding of the business. When that understanding is wrong, every new feature gets harder—not because of bad code, but because of a bad model.
Read article →- Domain-Driven Design
- Domain Modeling
What Does "Domain" Actually Mean in Software Development?
If you ask ten developers what domain means, you will get ten answers. Here is what the word actually means before DDD jargon gets in the way.
Read article →- Domain-Driven Design
- Architecture
Why CRUD Systems Rarely Need Domain-Driven Design
DDD solves complexity—not CRUD. Here's how to tell when your system is about storing data versus modeling real business behavior.
Read article →- Domain-Driven Design
- Domain Modeling
Why Your Code Should Speak the Business Language
If your code doesn't reflect how the business thinks, you'll spend forever translating between two worlds. Here's why naming like the domain experts matters.
Read article →