2 ms·
That quote stood out to me too. I read the DDD book twice, about 5 years apart, and despite the experience I gained between the two readings, I felt the section
by johnh-hn 1y ago
That quote stood out to me too. I read the DDD book twice, about 5 years apart, and despite the experience I gained between the two readings, I felt the section describing ubiquitous language was the most valuable. I've seen genuine improvements in teams who adopt that, but I'm not so fussed about the rest of the book.
- pydry 1y agoThe parts about how ubiquitous language and bounded contexts are correct and nonobvious but not novel - these concepts existed before under a myriad of other names. DDD is pretty threadbare on opinions about how to manage your "ubiquitous language" or slice up your domain into "bounded contexts" after discovering that these are important concepts. That was already about 1/4 of my job before I'd ever even heard of DDD and then I had people throwing the book at me like it explained these things. It doesn't. It works as a sales pitch to sell consulting I guess but is not a coherent framework for developing software.