I have been reading Domain-Driven Design by Eric Evans since last August. Although the topic is interesting, it has been difficult to read the book—at least for me.
Eric explains domain models in great detail but provides few practical examples. As a developer, I am primarily interested in implementation. So, I have to pause frequently in order to translate his ideas into code. Eventually I had to accept the fact that DDD is only guidance for modelling and that implementation decisions are left to the programmer. This realisation made the book more enjoyable.
Considering software development as an engineering discipline, we tend to be rigid in how we write programs. We think that technical problems can be solved by science and maths alone. But coding is also a creative activity. And we can say that in this art, DDD is both style and inspiration.
Leave a comment