<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>braindouche</author><text>Rails is &lt;i&gt;not&lt;/i&gt; an example. Rails was extracted from a single project codebase, Basecamp. Extracting a Solution Factory out of the solutions we make is a great idea, but starting with a factory-first mindset is what distracts and then breaks programmers.</text><parent_chain><item><author>jrochkind1</author><text>&amp;gt; I wonder if it would actually be better for software teams to build not the thing they want, but rather the thing that makes the thing they want.&lt;p&gt;Sounds so appealing to programmers, so much harder than it sounds. A dangerous fantasy many ships have broke upon.&lt;p&gt;The proposals of &amp;quot;yagni&amp;quot; and the &amp;quot;mvp&amp;quot; are in some sense a reaction to the danger.&lt;p&gt;On the other hand, when it works, it works. I&amp;#x27;d say Rails is an example.</text></item></parent_chain></comment><story><title>A hierarchy of software engineering discourse</title><url>https://uvwx.github.io/hierarchy.html</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>mannykannot</author><text>The &amp;#x27;notation&amp;#x27; level similarly seems to be promoting the use of DSLs, and everything you say here also applies there (maybe I&amp;#x27;m jaded, but on more than one occasion, I have had to deal with the consequences of an incomplete DSL that had no real justification, and was clearly developed for egocentric reasons. I have also come across exactly one DSL (not mine) that was both justified and well-done.)&lt;p&gt;More generally, I agree with the author on the importance of seeing a hierarchy here.</text><parent_chain><item><author>jrochkind1</author><text>&amp;gt; I wonder if it would actually be better for software teams to build not the thing they want, but rather the thing that makes the thing they want.&lt;p&gt;Sounds so appealing to programmers, so much harder than it sounds. A dangerous fantasy many ships have broke upon.&lt;p&gt;The proposals of &amp;quot;yagni&amp;quot; and the &amp;quot;mvp&amp;quot; are in some sense a reaction to the danger.&lt;p&gt;On the other hand, when it works, it works. I&amp;#x27;d say Rails is an example.</text></item></parent_chain></comment><story><title>A hierarchy of software engineering discourse</title><url>https://uvwx.github.io/hierarchy.html</url></story>