Sebastian Gebski's Reviews > Domain-Driven Design: Tackling Complexity in the Heart of Software

Actually, it's the 2nd time I've read that book. After the 1st time I was quite happy with what I've received - I've generally agreed to author's approach, even more: I've found it rather obvious ("so not a big deal") - I'd do pretty much the same in the example cases, I agree that those design decisions are more reasonable, etc.

Some time has passed, I've discussed DDD with several people on several occassions and I think now I got the value of this book: author does not only gives you the example of good design, but he provides you the rules / formulas how to achieve that. I didn't see that when I was reading DDD for the first time, because I'm doing design "automatically" / intuitively, so I've never really needed those rules (and I've ignored them, to put it bluntly).

But I have a problem with teaching people how to make a good design, how to make a difference between snapshotting reality and making a proper model. And here's where this book really excels, this is the first book I've seen that actually CAN make reader a better designed. Very recommended.