<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>alkonaut</author><text>It completely removes the fun though, if you only enjoy generalizing, optimizing, refactoring, designing, and take &lt;i&gt;zero&lt;/i&gt; pleasure in delivering an actual usable product. If the product is Doom this shouldn&amp;#x27;t be a problem - but for most of us the product is form validation or calculations involving plywood. Making frameworks and generalization is the only reason I manage to keep doing what I do. (I&amp;#x27;m exaggerating somewhat, but I think this is a clear distinction between two kinds of programmers those who love the code; and the craft, and those who like making products. Have too many of one kind and you&amp;#x27;ll ship a mess. Too many of the other and you&amp;#x27;ll never ship)</text><parent_chain><item><author>a3n</author><text>&amp;gt; Write your code for this game only - not for a future game. You’re going to be writing new code later because you’ll be smarter.&lt;p&gt;This really stood out for me. I&amp;#x27;m always tempted, while writing something specific, to generalize it. I try to resist that, when I recognize it. Writing a ThingThatImWritingFramework risks ThingThatImWriting never seeing the light of day, or never being used.</text></item></parent_chain></comment><story><title>Id Software Programming Principles</title><url>http://blog.felipe.rs/2017/02/25/id-software-programming-principles/</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>hermitdev</author><text>This is basically the Mythical Man Month in a few lines.&lt;p&gt;You once wrote something specific, and it was great. Then you had to write a second thing, and you remember things from the first, so why not make it more general for the inevitable 3rd, 4th, 5th to come? And, then, you fail to deliver the 2nd.</text><parent_chain><item><author>a3n</author><text>&amp;gt; Write your code for this game only - not for a future game. You’re going to be writing new code later because you’ll be smarter.&lt;p&gt;This really stood out for me. I&amp;#x27;m always tempted, while writing something specific, to generalize it. I try to resist that, when I recognize it. Writing a ThingThatImWritingFramework risks ThingThatImWriting never seeing the light of day, or never being used.</text></item></parent_chain></comment><story><title>Id Software Programming Principles</title><url>http://blog.felipe.rs/2017/02/25/id-software-programming-principles/</url></story>