<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>blunte</author><text>The AI coding approach is solving the wrong problem.  The problem isn&amp;#x27;t with the low level detailed work.  That problem should be solved by building composable, tested, audited libraries.  Legos, if you will.&lt;p&gt;If the problem is trivial enough that you can completely trust the AI coded solution, then you could have either done it yourself very easily or used a premade solution from a good library or toolkit.&lt;p&gt;If the problem is not trivial, then you have the outsourcing challenges (which apply to a lot more scenarios than using AI to help you code).&lt;p&gt;If you are not personally capable of judging the outsourced work, then whether you use AI or type it yourself, you will end up with errors or misfeatures.&lt;p&gt;If you are capable of judging, then you must pay attention and read&amp;#x2F;review.  So your job shifts from defining the problem and programming a solution to defining the problem and reviewing potential solution(s).  Either way, you must focus and think.  But again, perhaps you would be better off building a solution composed of known good blocks.  &amp;lt;- This should be the future of software development...&lt;p&gt;Sadly, I think that open source and freedom to (re)invent has worked against us in the long run.  If instead of each of us going off and thinking, &amp;quot;I can make a better language&amp;#x2F;framework&amp;quot;, we had built on existing technologies, I daresay we would be further along.  To be fair of course, some level of dissatisfaction and divergence would be necessary or we would still be using assembly.&lt;p&gt;Github does have one thing right though (from a business perspective) - they are making a remedy to a symptom, and in that they can expect longer term revenue than if they actually solved the core problem.</text><parent_chain></parent_chain></comment><story><title>GitHub Copilot: First Impressions</title><url>https://vladiliescu.net/github-copilot-first-impressions/</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>obviyus</author><text>I very recently got access to Copilot, while I was in the middle of learning and playing around with Clojure.&lt;p&gt;It’s surprisingly useful when you’re not sure about how you want to proceed. E.g. While I was trying to make a simple function for printing all palindromic numbers under 10,000, Copilot inferred from the function name what I was trying and suggested a function using threading macros (something I hadn’t yet come across in Clojure). The result was a much neater affair than what I came up with on my own. I feel it could be a fantastic way to build familiarity with a new language.</text><parent_chain></parent_chain></comment><story><title>GitHub Copilot: First Impressions</title><url>https://vladiliescu.net/github-copilot-first-impressions/</url></story>