<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>Thorrez</author><text>The third largest bitcoin exchange made a change to their RAM settings in EC2. This shut down the machines, wiping out the hard drive and RAM. Their wallet was stored there. They lost everything.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;siliconangle.com&amp;#x2F;2011&amp;#x2F;08&amp;#x2F;01&amp;#x2F;third-largest-bitcoin-exchange-bitomat-lost-their-wallet-over-17000-bitcoins-missing&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;siliconangle.com&amp;#x2F;2011&amp;#x2F;08&amp;#x2F;01&amp;#x2F;third-largest-bitcoin-ex...&lt;/a&gt;</text><parent_chain><item><author>inopinatus</author><text>There is a tale - perhaps apocryphal - handed down between generations of AWS staff, of a customer that was all-in on spot instances, until one day the price and availability of their preferred instances took an unfortunate turn, which is to say, all their stuff went away, including most dramatically the customer data that was on the instance storages, and including the replicas that had been mistakenly presumed a backstop against instance loss, and sadly - but not surprisingly - this was pretty much terminal for their startup.</text></item></parent_chain></comment><story><title>A million ways to die on the web</title><url>https://wiki.archiveteam.org/index.php/A_Million_Ways_to_Die_on_the_Web</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>BossingAround</author><text>How..? Was there no local code on any of the dev machines? No git? I&amp;#x27;m asking because for example if Github is vaporized today, my product would lose roughly a day or two&amp;#x27;s worth of work, since we have like 30 computers having a repository copy.&lt;p&gt;Of course redeploying every single thing would not be seamless because of course, there might be some configuration stored in services, or something similar, but I&amp;#x27;d say that ~90% of our automation is stored in Git.</text><parent_chain><item><author>inopinatus</author><text>There is a tale - perhaps apocryphal - handed down between generations of AWS staff, of a customer that was all-in on spot instances, until one day the price and availability of their preferred instances took an unfortunate turn, which is to say, all their stuff went away, including most dramatically the customer data that was on the instance storages, and including the replicas that had been mistakenly presumed a backstop against instance loss, and sadly - but not surprisingly - this was pretty much terminal for their startup.</text></item></parent_chain></comment><story><title>A million ways to die on the web</title><url>https://wiki.archiveteam.org/index.php/A_Million_Ways_to_Die_on_the_Web</url></story>