<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>nimithryn</author><text>If anything it&amp;#x27;s the reverse:
&amp;quot;NASA: 90% of our rocket scientists use the rocket you designed, but you can&amp;#x27;t fix an AC so f* off&amp;quot;</text><parent_chain><item><author>alexmlamb</author><text>Is it just me or does this reasoning not make any sense?&lt;p&gt;&amp;quot;NASA: 90% of our rocket scientists use the A&amp;#x2F;C you just fixed, but you can&amp;#x27;t explain how a rocket works so f* off&amp;quot;&lt;p&gt;Presumably what matters is whether homebrew is technically significant or relevant, not just that they use it?</text></item><item><author>fatnoah</author><text>Or put more succinctly:  &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;mxcl&amp;#x2F;status&amp;#x2F;608682016205344768?lang=en&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;mxcl&amp;#x2F;status&amp;#x2F;608682016205344768?lang=en&lt;/a&gt;&lt;p&gt;&amp;quot;Google: 90% of our engineers use the software you wrote (Homebrew), but you can’t invert a binary tree on a whiteboard so f&lt;i&gt;&lt;/i&gt;* off.&amp;quot;</text></item><item><author>palisade</author><text>I once interviewed at a company that had you write a traveling salesman program where you were planning the shortest path of flights between cities. It was a take home test where you were given at least a week to complete it. I completed the test in record setting time (3 days earlier than most), mine was the only one that was fully documented with comments (no one else bothered to do this), they said I had the most visually stunning user interface (most were ugly or unusable; I even animated the plane flying between cities), the program came to the outcome in the shortest runnable time, out of all the submitters they said my program was the most optimized solution (not the best ever made, but the best submitted to this company so far), and mine was the only one that actually worked correctly and ran without flaws. They then proceeded to have me come in for the 6 hour interview in which they asked questions like, &amp;quot;Write a working hash table from scratch on the whiteboard.&amp;quot; I got nervous and passed the question, they ended the interview early and rejected my application.</text></item></parent_chain></comment><story><title>Hiring Is Broken: What Do Developers Say About Technical Interviews?</title><url>https://www.researchgate.net/publication/334448588_Hiring_is_Broken_What_Do_Developers_Say_About_Technical_Interviews</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>musicale</author><text>I think it&amp;#x27;s just you.&lt;p&gt;0. The actual job of a software developer is usually to develop software with some real-world use and benefit, not to write cs101 code on a whiteboard while someone watches you and grades you for speed and accuracy.&lt;p&gt;1. Software is what Google does, and Google does tons of software from tools to infrastructure to services to games. If you created a key software tool that tons of people use at Google to do their jobs, it&amp;#x27;s pretty relevant.&lt;p&gt;2. Software isn&amp;#x27;t like doing routine maintenance on an existing A&amp;#x2F;C system - it&amp;#x27;s usually somewhere between inventing A&amp;#x2F;C and creating a new design for data center A&amp;#x2F;C systems then building, deploying, and operating it.</text><parent_chain><item><author>alexmlamb</author><text>Is it just me or does this reasoning not make any sense?&lt;p&gt;&amp;quot;NASA: 90% of our rocket scientists use the A&amp;#x2F;C you just fixed, but you can&amp;#x27;t explain how a rocket works so f* off&amp;quot;&lt;p&gt;Presumably what matters is whether homebrew is technically significant or relevant, not just that they use it?</text></item><item><author>fatnoah</author><text>Or put more succinctly:  &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;mxcl&amp;#x2F;status&amp;#x2F;608682016205344768?lang=en&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;mxcl&amp;#x2F;status&amp;#x2F;608682016205344768?lang=en&lt;/a&gt;&lt;p&gt;&amp;quot;Google: 90% of our engineers use the software you wrote (Homebrew), but you can’t invert a binary tree on a whiteboard so f&lt;i&gt;&lt;/i&gt;* off.&amp;quot;</text></item><item><author>palisade</author><text>I once interviewed at a company that had you write a traveling salesman program where you were planning the shortest path of flights between cities. It was a take home test where you were given at least a week to complete it. I completed the test in record setting time (3 days earlier than most), mine was the only one that was fully documented with comments (no one else bothered to do this), they said I had the most visually stunning user interface (most were ugly or unusable; I even animated the plane flying between cities), the program came to the outcome in the shortest runnable time, out of all the submitters they said my program was the most optimized solution (not the best ever made, but the best submitted to this company so far), and mine was the only one that actually worked correctly and ran without flaws. They then proceeded to have me come in for the 6 hour interview in which they asked questions like, &amp;quot;Write a working hash table from scratch on the whiteboard.&amp;quot; I got nervous and passed the question, they ended the interview early and rejected my application.</text></item></parent_chain></comment><story><title>Hiring Is Broken: What Do Developers Say About Technical Interviews?</title><url>https://www.researchgate.net/publication/334448588_Hiring_is_Broken_What_Do_Developers_Say_About_Technical_Interviews</url></story>