Domain-Driven Design by Eric Evans

What worked & what was valuable in the quest

This book is long, but great at helping programmers see how to make their code more and more valuable for the business, as well as more and more flexible along axes of change that are likely in the particular domain.

What didn't work, what you'd change next time

This is a book I should've read a long, long time ago. I enjoyed it though!

What you learned (related items from the Skills Inventory)

My summary.

Reviewers, please comment below: