Words, words, everywhere, and not a line of code

OK, there are a *few* lines of code.

The ideas presented in the book are well worth understanding, but the presentation is so unbelievably dry that it's just a slog. I disagree with those reviewers who say that the book is difficult because the ideas themselves are difficult -- I have been able to explain the ideas to other devs over lunch, once I got them myself. The main problem with book is the writing, and the main problem with the writing is not that it's too dense, but that it isn't dense enough. He goes on for tens of pages explaining concepts that could be explained in a page and a few good examples by a less windy writer. The other main problem with the book is that there is very little code, so rather than showing you, he's telling you (and telling you, and telling you). There are lots of sentences like, "Because the Shipping Service has an indirect dependency on the Cargo object and the Cargo object has a bidirectional association with the Customer class..." Huh? Bust out some code! Code is an concise, unambiguous representation of the programmer's intentions (which, ironically, he makes a point of mentioning several times), but instead of taking advantage of this, he tries to explain everything with words. Lots and lots of words.

In conclusion: Read the e-book instead. It's a 104-page summary of the main ideas of DDD. You'll actually get to the end.

Other Reviews

• Great Intro to DDD
• Words, words, everywhere, and not a line of code
• It's a must read for life, which is when you'll maybe understand it
• Kandinskian Driven Design