<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>jdlshore</author><text>The book that introduced the term, “Domain-Driven Design” by Eric Evans, is thick but excellent.</text><parent_chain><item><author>seanwilson</author><text>&amp;gt; Software for a complex domain requires all designers (engineers, testers, analysts, …) to have a deep, shared understanding of the domain, guided by domain experts ... That understanding is rooted in language: the domain language should be formalised into a Ubiquitous Language (shared, agreed upon, unambiguous) ...&lt;p&gt;&amp;gt; DDD is not prescriptive. It doesn’t have rules of how to do it, and is open to new interpretation. It doesn’t prescribe methods, or practices, and even the patterns in the book1 are meant to be illustrative rather than a final set. ...&lt;p&gt;&amp;gt; That makes DDD notoriously hard to define.&lt;p&gt;I don&amp;#x27;t know anything about DDD, but if you can&amp;#x27;t concretely describe it and how it&amp;#x27;s different to how teams naturally work together, how can it be actionable and what stops it becoming another cargo cult when nobody can agree on what it is?</text></item></parent_chain></comment><story><title>Domain-Driven Design</title><url>https://verraes.net/2021/09/what-is-domain-driven-design-ddd/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>athrun</author><text>I recently came across this talk from Scott Wlaschin titled &amp;quot;Domain Modeling Made Functional&amp;quot;.&lt;p&gt;I found it a great practical introduction to DDD.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.youtube.com&amp;#x2F;watch?v=PLFl95c-IiU&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.youtube.com&amp;#x2F;watch?v=PLFl95c-IiU&lt;/a&gt;</text><parent_chain><item><author>seanwilson</author><text>&amp;gt; Software for a complex domain requires all designers (engineers, testers, analysts, …) to have a deep, shared understanding of the domain, guided by domain experts ... That understanding is rooted in language: the domain language should be formalised into a Ubiquitous Language (shared, agreed upon, unambiguous) ...&lt;p&gt;&amp;gt; DDD is not prescriptive. It doesn’t have rules of how to do it, and is open to new interpretation. It doesn’t prescribe methods, or practices, and even the patterns in the book1 are meant to be illustrative rather than a final set. ...&lt;p&gt;&amp;gt; That makes DDD notoriously hard to define.&lt;p&gt;I don&amp;#x27;t know anything about DDD, but if you can&amp;#x27;t concretely describe it and how it&amp;#x27;s different to how teams naturally work together, how can it be actionable and what stops it becoming another cargo cult when nobody can agree on what it is?</text></item></parent_chain></comment><story><title>Domain-Driven Design</title><url>https://verraes.net/2021/09/what-is-domain-driven-design-ddd/</url></story>