Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I had the reaction when reading a preprint of Domain Driven Design. It was packed with ideas which were just coming into focus in my own mind after 10 years in the industry, but I didn't have names for them or have them systematized. It's a terrific feeling reading a well-written book like that and going 'Yes! Yes! Yes!'.

(Since then, as with many things in our industry, it seems the book has been turned into a buzzword consulting/training money grab. Sigh.)



When I first read the DDD book almosty 15 years ago, I think it took me 2 or 3 reads to get it into my head. I really like the first half that can be used purely for a design perspective, and the second half for communicating with the business people to do business domain modelling .

Other books I really like are

The Design of Everyday Things by Don Norman, it is a good read and lets you talk to a lot of UX'ers as I have found more than a few that have used this book for their thesis.

Enterprise Integration Patterns by Gregor Hohpe and Bobby Woolf, which is old but in world of streaming procesing a lot of the patterns can be reused.

The Site Reliability Engineering books or their free counter parts found on https://landing.google.com/sre/books/

edited to add a couple of newlines.


The book itself has turned into a consulting money grab, or DDD as a concept?


It looks like (to me) there is a DDD training industry, along the lines of, or as a part of the “agile transformation“ training industry.

Which in and of itself isn’t bad I suppose, but part of me feels that these are cynical attempts to unscrupulously monetize ideas who’s time has come by bombarding credulous middle management with buzzwords.


Seconding this question as a reddit remindMe.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: