We’re considering using GitHub Copilot to speed up our dev work — have you tried it? What was your experience?

3.3k views2 Upvotes5 Comments

CTO in Transportation, 11 - 50 employees
We did tried and it could help to reduce some of the repetitive boilerplate or even in some cases gave you a few options of the code that you could write.

But we decided not to use because in many cases the code suggested had problems both related to performance, quality and security.

If you could make sure your team uses it in a limited kind of powerful autocomplete but they don’t take whole chunks of code from it, it may help.

We plan to re-evaluate in a years time but our main concern is still quality and code security.
Group Engineering Manager, Self-employed
Its a bit over hyped on just how much time it will save you.  Its good at auto completion and speeding up redundant tasks like adding imports and creating initial classes but you wont find it saving 50% of your time like some articles claim.
1 2 Replies
Director of IT in Healthcare and Biotech, 1,001 - 5,000 employees

Did you develop any guidelines or policies around the use of GitHub Copilot?

Group Engineering Manager, Self-employed

We will eventually but in the initial pilots we ran we did not.  There is obviously a high cost associated with it so we need to evaluate the question of WHO and we also need to figure out the WHAT.  We still have some concerns with what all we allow copilot to consume that we are working through as a company.

CDO in Software, 10,001+ employees
We have tried it for many years. It’s great as a learning tools for junior developers but with some overseeing of an expert developer. That is why it’s a copilot and not a pilot (yet). I think it will accelerate your developers work, no doubt, just make sure people check the quality of the suggestions. It’s becoming a sensible default to use it, with caution.

Content you might like

We lack AI governance policies24%

We’re banned from using these tools37%

Our staff and/or leadership are resistant38%

We have concerns about the results being generated43%

We have third-party security and risk concerns27%

We don’t trust current vendors4%




CTO in Software, 201 - 500 employees
Without a doubt - Technical Debt! It's a ball and chain that creates an ever increasing drag on any organization, stifles innovation, and prevents transformation.
Read More Comments
43.5k views132 Upvotes319 Comments

<6 months8%

6-12 months54%

12-18 months24%

18-24 months7%

>24 months5%


2.8k views5 Upvotes2 Comments