<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>mancerayder</author><text>&lt;i&gt;On my ops team, we&amp;#x27;ve gotten some flak for not building robust enough of a request queue for some tasks. But it&amp;#x27;s been down several hours in the past year. The server almost never needs maintenance. None of the workload is real-time. App restarts are acceptable if memory leaks occur.&lt;p&gt;If we did everything by the enterprise book, we&amp;#x27;d still be 70% of the way to a deployed product, instead of 15 months into its completion.&lt;/i&gt;&lt;p&gt;Sure.  Except if this Ops team is like most Ops teams, they&amp;#x27;d prefer to do it the (cue dark, brooding orchestral dum-dum-dum musical interlude) &amp;#x27;enterprise&amp;#x27; way rather than be woken up by PagerDuty in the middle of the night because a new release push lead to the CPU spiking.&lt;p&gt;Sorry, but I&amp;#x27;ve almost never seen situations where people have skimped on HA and someone else didn&amp;#x27;t get excoriated during an outage.&lt;p&gt;Maybe other people&amp;#x27;s experiences are different, but as a DevOps guy, even in a relatively new environment, my priority is stability.  Not faith-based-computing based on someone&amp;#x27;s positive seat-of-their-pants past experience.</text><parent_chain><item><author>unethical_ban</author><text>On the flip side, when something DOESN&amp;#x27;T need HA, sub-millisecond query response time, or lynx and IE Edge compatability, people need to know when &amp;quot;good enough&amp;quot; is good enough.&lt;p&gt;On my ops team, we&amp;#x27;ve gotten some flak for not building robust enough of a request queue for some tasks. But it&amp;#x27;s been down several hours in the past year. The server almost never needs maintenance. None of the workload is real-time. App restarts are acceptable if memory leaks occur.&lt;p&gt;If we did everything by the enterprise book, we&amp;#x27;d still be 70% of the way to a deployed product, instead of 15 months into its completion.</text></item></parent_chain></comment><story><title>I wrote the SQL query in 5 mins. Why does my engineer say it will take a month?</title><url>https://wtfismyengineertalkingabout.com/2017/03/11/i-wrote-the-sql-query-in-5-mins-why-does-my-engineer-say-it-will-take-a-month/</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>arethuza</author><text>I once had an infrastructure guy who worked in the same company quote me £70K for new hardware to host a single static HTML web page.&lt;p&gt;£70K of new hardware!&lt;p&gt;I stuck it on an existing server and nobody noticed though I might have got into trouble with the Change Prevention Board for not using the right form or something...&lt;p&gt;Edit: He did have a carefully worked out explanation of where the money had to be spent.... which I ignored after hearing &amp;quot;£70K&amp;quot;.</text><parent_chain><item><author>unethical_ban</author><text>On the flip side, when something DOESN&amp;#x27;T need HA, sub-millisecond query response time, or lynx and IE Edge compatability, people need to know when &amp;quot;good enough&amp;quot; is good enough.&lt;p&gt;On my ops team, we&amp;#x27;ve gotten some flak for not building robust enough of a request queue for some tasks. But it&amp;#x27;s been down several hours in the past year. The server almost never needs maintenance. None of the workload is real-time. App restarts are acceptable if memory leaks occur.&lt;p&gt;If we did everything by the enterprise book, we&amp;#x27;d still be 70% of the way to a deployed product, instead of 15 months into its completion.</text></item></parent_chain></comment><story><title>I wrote the SQL query in 5 mins. Why does my engineer say it will take a month?</title><url>https://wtfismyengineertalkingabout.com/2017/03/11/i-wrote-the-sql-query-in-5-mins-why-does-my-engineer-say-it-will-take-a-month/</url></story>