11
The failed promise of Domain-Driven Design - part 1
(no-kill-switch.ghost.io)
"Domain-Driven Design is an approach to software development that centers the development on programming a domain model that has a rich understanding of the processes and rules of a domain. The name comes from a 2003 book by Eric Evans that describes the approach through a catalog of patterns. Since then a community of practitioners have further developed the ideas, spawning various other books and training courses. The approach is particularly suited to complex domains, where a lot of often-messy logic needs to be organized." -- Martin Fowler (link)
Rules
No, DDD isn't very helpful. It has only high-level concepts and it's hard to specialize into one's work.
But then, DDD is the most helpful technique we have. It's the one used every single time a project is successful, and for good reasons.