imnos

imnos t1_iy0xy2v wrote

Er, a lot? If your codebase is well structured most of it will follow similar patterns which you just need to repeat, with different class/variable names etc. That makes it ripe for automation with Copilot.

Then there's unit tests which cover the above - if you keep the structure similar then copilot can fly through it.

Likewise for generating things like seed data. Need to create some seeds for your database just write out what you need in a comment and Copilot gets it mostly right.

So much time saved.

1

imnos t1_iy0wz76 wrote

I've been coding for 5+ years professionally so I mostly use it to save the effort of typing.

You need to be able to look at what Copilot spits out and understand if it's correct or not, so I'd say it wouldn't be much use for a newbie. You have to know how to structure your code and then let Copilot fill things out whilst keeping an eye on what it's doing.

Sometimes it saves me Googling something I don't know how to do if I can instruct it correctly - and then I just test that what it wrote works, so you may be able to learn some things from it but you'll be able to use it to it's full potential once you have some knowledge/experience under your belt.

3

imnos t1_ixyvu0j wrote

I'm not sure if it's safe for a decade but I've been using Copilot for over a year and it's a huge time saver like you say. 90% of the time it gets what I need with at least 90% accuracy. Really helpful for writing repetitive code.

I find it works best if your codebase is consistent and well structured.

With GPT-4 on the horizon, and DeepMind also having a model that can compete with "the average developer", I'm super interested to see how things change in the next few years.

24