Domain Driven Design

How to Easily Implement Domain Driven Design - A Quick & Simple Guide

By: Jason Scotts

Narrated by: Chris Brinkley

I want to thank you for checking out the audiobook Domain Driven Design: How to Easily Implement Domain Driven Design - A Quick & Simple Guide. This book contains proven steps and strategies on how you can implement the domain-driven design approach in your projects to bring out better results.

Through the domain-driven design approach, you and your project team will better understand the domain that you aim to serve and communicate in a common language that can ensure harmony and team work with your group. You will be able to finish the whole design and development process focused on what is truly essential. Thanks again and I hope you enjoy it!

©2014 Yap Kee Chong (P)2014 Yap Kee Chong

too short, not very useful

I don't understand the purpose of this audiobook. Who is it intended for? For people who already read the major DDD books, and struggled to implement? This book didn't discuss pitfalls of implementing DDD. For those struggling to understamd the concepts? I'm pretty sure other more extensive books are better at this.

few examples, but to the point

not enough examples to better understand application of the concepts explained, and how they fit together

Lots of "What," but very little "Why" and almost zero "How."

Very superficial book that gives you a fast overview of DDD, but doesn't go deep into anything. I walked away knowing a few more jargon terms, but zero knowledge on how to approach a problem with a DDD perspective.

Practically zero information value

the book has very little usefulness for anyone even vaguely familiar with the term domain-driven design.

No idea who would find this helpful...

This book wasn’t for you, but who do you think might enjoy it more?

Maybe as passing background for a student going into an OOP 101 class?

Any additional comments?

This book does nothing more that indicate that the author has a working knowledge of DDD - it does not provide the listener with any actionable information or impart a concise understanding of what DDD is. It does not explain how DDD might uniquely affect software development. It does not give examples of techniques for distributing DDD knowledge except to discourage UML diagrams and say that "pictures" and "documentation" can be useful.

This book is so general in it's description of DDD and discussion of software development strategies, that nobody in the industry will learn anything (much) new. It is so technical that nobody outside a the development world will get any value from it either.

Unfortunately I can't find any other DDD audio books so I spent the $2.75 or whatever. I didn't think I'd regret spending $3, but it turns out I'm wrong. Put your $3 towards a hardcopy of Eric Evans book.