Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Domain-Driven Design Quickly Paperback – December 21, 2007
Dummies spring into summer sale
Save up to 40% on dummies guides to health, home, tech, money, and more. Shop now. See more
Customers who viewed this item also viewed
Browse award-winning titles. See more
If you are a seller for this product, would you like to suggest updates through seller support?
Top Customer Reviews
I was expecting upon reading the description of this text that it would simply be a highly consolidated reference to the definitions created in Eric Evan's DDD. I was hoping that there would be a few instructional chapters, with the focus being on the correlations of the DDD concepts. I was hoping I could quickly and decisively refresh my memory on the terms of DDD by briefly skimming this text. Instead I found myself muddling through a long ramble where every second or third sentence requires careful inspection to ascertain what the intended statement is.
Unfortunately, this paper reads like it was written in just a couple of days. The author uses prose throughout, and the text is in desperate need of an editor. Words that don't exist, unnecessary punctuation and other grammatical mistakes litter the text. Normally I wouldn't be too concerned about this except that the vast majority of the text suffers from this problem. It's actually quite distracting.
Honestly, I've got a very bad feeling about DDD after reading this "short introduction". Too much blah-blah! And I'm still today disinterested in finding out more. Despite the fact DDD was largely adopted as an Agile practice and I should definitely read more on the topic from a better source, I know it.
And you know what, it gets even better. You don't even have to read the whole 95 pages. IMO, the book is extremely well organized, and the reader can glean some important concepts just from skimming it in a first pass. Thereafter, as needed, the book serves very well as a handy reference.
I post this review after pulling it off the shelf to help me convince a newly formed group that we need a "What Should This Thing Do?" wiki page in addition to a "Deliverables" wiki page.