<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>ineedasername</author><text>That&amp;#x27;s not an argument not to optimize, that&amp;#x27;s an argument to consider the costs &amp;amp; implications of optimization. Failing to do that now can cost much more later on when compute resources need balloon and product scope&amp;#x2F;codebase is much larger, making optimizations more labor intensive.&lt;p&gt;There&amp;#x27;s no yes&amp;#x2F;no on this. It&amp;#x27;s all on a slider, a spectrum.</text><parent_chain><item><author>Scotrix</author><text>We’re a startup and focussed on easy horizontal scalability early on. From a management point of view premature optimizations are cost intensive, especially while we’re still figuring out what our product is and how it works. At the end there are a lot of changes all the time to functionality and implementation and optimizations early get wasted very quickly. We rather purchase new servers. A powerful server cost 100 USD&amp;#x2F;month and wehe development team can focus on implementing features and functionality which moves our product forwar d, optimizations are opportunity losses at the beginning of a product. Of course, as soon as bad performance impacts user experience it’s a different story and also if you start to have hundreds or thousands of servers but then you’ll know what your product is doing and changes become smaller, focused and code optimizations    start to make sense.</text></item></parent_chain></comment><story><title>Optimizing Your Web App 100x Is Like Adding 99 Servers</title><url>https://lukerissacher.com/blog/optimizing_your_web_app</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>curyous</author><text>What about the cost of putting shitty, slow software into the world?&lt;p&gt;How about having respect for you user&amp;#x27;s time? Depending on how many users you have, shaving seconds or milliseconds off your response time will save humanity hundreds, thousands, or millions of hours waiting for your software to do something.</text><parent_chain><item><author>Scotrix</author><text>We’re a startup and focussed on easy horizontal scalability early on. From a management point of view premature optimizations are cost intensive, especially while we’re still figuring out what our product is and how it works. At the end there are a lot of changes all the time to functionality and implementation and optimizations early get wasted very quickly. We rather purchase new servers. A powerful server cost 100 USD&amp;#x2F;month and wehe development team can focus on implementing features and functionality which moves our product forwar d, optimizations are opportunity losses at the beginning of a product. Of course, as soon as bad performance impacts user experience it’s a different story and also if you start to have hundreds or thousands of servers but then you’ll know what your product is doing and changes become smaller, focused and code optimizations    start to make sense.</text></item></parent_chain></comment><story><title>Optimizing Your Web App 100x Is Like Adding 99 Servers</title><url>https://lukerissacher.com/blog/optimizing_your_web_app</url></story>