<story><title>GitHub Copilot for individuals available without waitlist, with free trial</title><url>https://github.com/features/copilot</url></story><parent_chain><item><author>happyhardcore</author><text>I&amp;#x27;ve found copilot invaluable for throwing together quick scripts, especially in languages I don&amp;#x27;t quite understand. Writing e.g. a bash script, and being able to add a comment saying&lt;p&gt;&lt;pre&gt;&lt;code&gt;    # Print an error message in red and exit if this program returns an error
&lt;/code&gt;&lt;/pre&gt;
and have it print out&lt;p&gt;&lt;pre&gt;&lt;code&gt;    if ! some_program
    then
        echo -e &amp;quot;\e[31msome_program failed\e[0m&amp;quot;
        exit 1
    fi
&lt;/code&gt;&lt;/pre&gt;
makes it so much quicker to cobble together something that works without having to context switch and go Google something. That being said, I&amp;#x27;ve found when writing more complex code it has a real tendency to introduce subtle bugs that can really catch you out if you&amp;#x27;re not paying attention.&lt;p&gt;Purely from the amount of time I&amp;#x27;ve saved I&amp;#x27;d say it&amp;#x27;s well worth the $10&amp;#x2F;mo for my employer (it only has to save a few minutes a day to be worthwhile). Very excited to see how they improve it in the future!</text></item></parent_chain><comment><author>dagw</author><text>&lt;i&gt;I&amp;#x27;ve found when writing more complex code it has a real tendency to introduce subtle bugs that can really catch you out if you&amp;#x27;re not paying attention.&lt;/i&gt;&lt;p&gt;Yea, that is basically my experience as well. On balance I feel I wasted about as much time debugging broken copilot code as I&amp;#x27;ve saved from using it.</text></comment>
<story><title>GitHub Copilot for individuals available without waitlist, with free trial</title><url>https://github.com/features/copilot</url></story><parent_chain><item><author>happyhardcore</author><text>I&amp;#x27;ve found copilot invaluable for throwing together quick scripts, especially in languages I don&amp;#x27;t quite understand. Writing e.g. a bash script, and being able to add a comment saying&lt;p&gt;&lt;pre&gt;&lt;code&gt;    # Print an error message in red and exit if this program returns an error
&lt;/code&gt;&lt;/pre&gt;
and have it print out&lt;p&gt;&lt;pre&gt;&lt;code&gt;    if ! some_program
    then
        echo -e &amp;quot;\e[31msome_program failed\e[0m&amp;quot;
        exit 1
    fi
&lt;/code&gt;&lt;/pre&gt;
makes it so much quicker to cobble together something that works without having to context switch and go Google something. That being said, I&amp;#x27;ve found when writing more complex code it has a real tendency to introduce subtle bugs that can really catch you out if you&amp;#x27;re not paying attention.&lt;p&gt;Purely from the amount of time I&amp;#x27;ve saved I&amp;#x27;d say it&amp;#x27;s well worth the $10&amp;#x2F;mo for my employer (it only has to save a few minutes a day to be worthwhile). Very excited to see how they improve it in the future!</text></item></parent_chain><comment><author>croes</author><text>Maybe they can replace you with copilot and an unexperienced cheaper user.</text></comment>