DDD seems to be one of those things where 'what it's meant to mean' is very different from 'how it's actually practiced'. Reading about what it's meant to mean

DDD seems to be one of those things where 'what it's meant to mean' is very different from 'how it's actually practiced'. Reading about what it's meant to mean, it seems pretty common sense. As often implemented, however, it seems to lead to a lot of accidental complexity and a bunch of dubious usefulness abstraction layers. I have a theory why this is. It seems that enterprise development as a field have a penchant for methodologies and acronyms. So, whatever silver bullet the enterprise-y shops get interested in eventually gets enterprisified. Be it UML, OOP, Agile, or DDD. EDIT: I've found this an interesting read that sheds some more light on DDD using counter-examples: http://media.pragprog.com/titles/swdddf/understand.pdf http://media.pragprog.com/titles/swdddf/understand.pdf