<p>“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 (<a href="https://martinfowler.com/bliki/DomainDrivenDesign.html" rel="nofollow">link</a>)</p>
<p><strong>Rules</strong></p>
<ol>
<li>Follow programming.dev rules</li>
<li>Be excellent to each other, no hostility towards users for any reason</li>
<li>No spam of tools/companies/advertisements. It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.</li>
</ol>