<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>sgtnoodle</author><text>Lol, I alternate between aero-press and pour over depending on the grounds I currently have. My tolerance for latency for good coffee is high regardless of how urgent other folk are for my time! Not that I&amp;#x27;m a snob about coffee, I have instant on hand for convenience as well, and I&amp;#x27;ll happily drink a poorly brewed cup too. It&amp;#x27;s just a nice ritual and something to optimize for fun.</text><parent_chain><item><author>ineedasername</author><text>The low latency approach is pretty much already encapsulated by the MVP approach to product design and incremental release schedule. Actually, considering the lower overhead of testing &amp;amp; implementation for small incremental changes vs. monolithic releases that are much harder to reverse course if there&amp;#x27;s a problem, the low-latency approach could also be the higher throughput approach.&lt;p&gt;Anyway, I am literally going to make myself one single cup of coffee now. No one in my house drinks it, so I have tried just about every method of making a single good cup of coffee. Right now, that balances towards very low latency but very low quality: instant coffee, because my tolerance for coffee latency is usually very low. (also low tolerance for cleaning up the equipment needed to make coffee-- garbage collection!) At some point the needle will swing back towards quality and I&amp;#x27;ll take the extra 5 minutes to do a pour over &amp;amp; deal with cleaning more stuff.</text></item></parent_chain></comment><story><title>Inefficient Efficiency (2019)</title><url>https://medium.com/@kentbeck_7670/inefficient-efficiency-5b3ab5294791</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>bonniemuffin</author><text>If you&amp;#x27;re not very cost-conscious, you can get excellent instant coffee (e.g. Sightglass), but it&amp;#x27;ll cost you &amp;gt;$2.50&amp;#x2F;cup, much more than equivalent quality beans.&lt;p&gt;Yet another instance of fast&amp;#x2F;cheap&amp;#x2F;good, pick two.</text><parent_chain><item><author>ineedasername</author><text>The low latency approach is pretty much already encapsulated by the MVP approach to product design and incremental release schedule. Actually, considering the lower overhead of testing &amp;amp; implementation for small incremental changes vs. monolithic releases that are much harder to reverse course if there&amp;#x27;s a problem, the low-latency approach could also be the higher throughput approach.&lt;p&gt;Anyway, I am literally going to make myself one single cup of coffee now. No one in my house drinks it, so I have tried just about every method of making a single good cup of coffee. Right now, that balances towards very low latency but very low quality: instant coffee, because my tolerance for coffee latency is usually very low. (also low tolerance for cleaning up the equipment needed to make coffee-- garbage collection!) At some point the needle will swing back towards quality and I&amp;#x27;ll take the extra 5 minutes to do a pour over &amp;amp; deal with cleaning more stuff.</text></item></parent_chain></comment><story><title>Inefficient Efficiency (2019)</title><url>https://medium.com/@kentbeck_7670/inefficient-efficiency-5b3ab5294791</url></story>