More and more I'm coming to the opinion that #DDDesign is not as popular as it could be because it's not speaking to the "just tell me how to do X" crowd.
I honestly don't know how to convey that it doesn't work like that, with the important bits of DDD being outside of code.
I honestly don't know how to convey that it doesn't work like that, with the important bits of DDD being outside of code.
Aggregates, Entities, Value objects, and other tactical patterns are not at the core, and adopting them on their own will most probably not lead to any significant benefit, while it will certainly introduce ceremony in code
Also, we don't adopt #DDDesign for its own sake. We adopt practices within a system: the system of a company building a product, and similar to all systems it can be influenced unpredictably by adopting something in isolation. It's _always_ better to consider changes holistically