<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>arjie</author><text>That&amp;#x27;s just how we learn to apply things correctly. If the first time you use a tool is to build a scale-appropriate project, you will stumble and likely fail.&lt;p&gt;Imagine you want to sail across the Atlantic and, to acclimate to the necessary tasks, you started small: sailing down the Thames, then sailing to Calais, then sailing farther and into the deeper ocean, before you decide to take the big trip. Now imagine you posted a blog post about this, and the first thing someone pointed out is that you can take the ferry to Calais.&lt;p&gt;That&amp;#x27;s what you&amp;#x27;ve done.</text><parent_chain><item><author>jbreckmckye</author><text>I feel a little mixed about projects like this.&lt;p&gt;It&amp;#x27;s fantastic to see people share their knowledge, and turn theory into practice. It&amp;#x27;s very easy to spout on about best practices and good ideas without demonstrating how they can be implemented in the real world. And this application does demonstrate some good ideas.&lt;p&gt;...But some bad ideas also. I think one problem we have in the frontend world is that developers of very small, very simple sites are pulling in solutions entirely unsuited to their scale of problems. They think they are being careful and investing in an insurance against rapid expansion, but what they&amp;#x27;re actually doing is overspending on the wrong investments, making things expensive that don&amp;#x27;t need to be expensive, and betting against agility. This seems like a mistake.&lt;p&gt;I encounter too many teams who are building web applications by bunding a cornucopia of technologies they don&amp;#x27;t understand and allow &amp;quot;best practice&amp;quot; examples on GitHub and Medium to do their decision-making for them. They disengage critically from their technology choices, which has the short term benefit of getting them moving faster, but the long term cost of never developing their research and evaluation skills.&lt;p&gt;This is not your fault, of course. People always want a silver bullet, a framework prefabricated and ready for drop-in domain code. And to be fair, most websites are very like each other. I just wish software developers chose their tech a little more critically.</text></item></parent_chain></comment><story><title>Hacker News Clone Using GraphQL and React</title><url>https://github.com/clintonwoo/hackernews-react-graphql</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>techaddict009</author><text>This is exactly what I feel. I get heavy request to build projects in React where their use case is pretty simple even wordpress can suffice.</text><parent_chain><item><author>jbreckmckye</author><text>I feel a little mixed about projects like this.&lt;p&gt;It&amp;#x27;s fantastic to see people share their knowledge, and turn theory into practice. It&amp;#x27;s very easy to spout on about best practices and good ideas without demonstrating how they can be implemented in the real world. And this application does demonstrate some good ideas.&lt;p&gt;...But some bad ideas also. I think one problem we have in the frontend world is that developers of very small, very simple sites are pulling in solutions entirely unsuited to their scale of problems. They think they are being careful and investing in an insurance against rapid expansion, but what they&amp;#x27;re actually doing is overspending on the wrong investments, making things expensive that don&amp;#x27;t need to be expensive, and betting against agility. This seems like a mistake.&lt;p&gt;I encounter too many teams who are building web applications by bunding a cornucopia of technologies they don&amp;#x27;t understand and allow &amp;quot;best practice&amp;quot; examples on GitHub and Medium to do their decision-making for them. They disengage critically from their technology choices, which has the short term benefit of getting them moving faster, but the long term cost of never developing their research and evaluation skills.&lt;p&gt;This is not your fault, of course. People always want a silver bullet, a framework prefabricated and ready for drop-in domain code. And to be fair, most websites are very like each other. I just wish software developers chose their tech a little more critically.</text></item></parent_chain></comment><story><title>Hacker News Clone Using GraphQL and React</title><url>https://github.com/clintonwoo/hackernews-react-graphql</url></story>