Implementing Domain-Driven Design


Eric’s Domain-Driven Design (DDD) book is unfortunately not seen enough on software engineers desks.  Hopefully, Implementing Domain-Driven Design will increase the usage of DDD.  Having started to read the book on the last flight, I think Vaughn makes a number of comments in the early pages that are spot on.  Specifically:

“General abandonment of good design and development practices in the Java community” (page xxvii)

“Scrum and other agile techniques are being used as a substitute for careful modelling, where a product backlog is thrust at developers as if it serves as a set of designs” (page xxvii)

“A good portion of our industry is made up of sample code followers, which isnt bad as long as the samples are quality ones” – unfortunately a lot of samples focus on demonstrating API’s, ignoring good design principles. (page 14)

Finally, as is often the case, the small details make a big difference.  An ubiquitous Language offers many advantages, one being the ability to demonstrate the code to domain experts to ensure that the tests are adhering to the ubiquitous language based on the current meaning.

~ by mdavey on September 16, 2014.

One Response to “Implementing Domain-Driven Design”

  1. Hokey dokey, then. I’ll keep that in mind.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: