The Beauty of Designing Software
Very few people realize that the Big Blue Book is also an ultimate guide to category design.
Domain-Driven Design is about building a culture of thinking in domain concepts, discovering important domain insights, and creating a new language around them.
And the word design matters.
Design is not mechanical implementation. It is the creative process of deciding how a problem should be understood and expressed.
Eric Evans compares software design to the creativity required to make a movie. Like a director, software designers intentionally choose which story to tell:
Which concepts are important?
Which ones should be ignored?
What language best expresses the domain?
What model makes the system coherent?
Every domain can be represented in infinitely many ways. The model does not simply emerge from reality - it is an intentionally designed, artificial version of it.
That is why writing code was never the real bottleneck.
The bottleneck is discovering the right concepts, choosing the right abstractions, and composing them into a model that reveals something previously hidden.
Even the book cover communicates this idea.
It features Composition VIII by Wassily Kandinsky - a work filled with abstractions, colors, shapes, and new visual concepts, composed into one coherent piece of art.
Composition VIII (1923) by Wassily Kandinsky — the artwork on the cover of Eric Evans’ Domain-Driven Design.
That is what software development can become when we truly apply Domain-Driven Design.
Not task execution. Not mechanical decomposition. A creative act of discovering and designing a new language for the domain.
With tools and technology we already have, we can build much more valuable systems than most projects today. We can write software that is a pleasure to use and a pleasure to work on; software that doesn't box us in as it grows, but creates new opportunities and continues to add value for its owners.
