4 ms·

I've been experimenting with copilot for a few months now and it has been really fun/frustrating. As the post mentions - it's best for fullstack development or

I've been experimenting with copilot for a few months now and it has been really fun/frustrating. As the post mentions - it's best for fullstack development or learning new languages/toolsets. However, the error rate is still too high for a pure productivity booster, thus it still feels like a fun novelty. For example, it would help me out with 4 functions and the 5th one would be just plain, confidently wrong and all of those gains are spent on debugging the error. I noticed this especially sucky on lower-level languages or more niche libraries. I was learning Go and it just kept producing errors, introducing unused imports etc. while in Python it can straight up complete my JSON parser predicting the keys and everything. I wish it had some sort of verbosity setting - this would greatly help with trust. If it outputs some code with single character variables, no comments and some magic comprehension and I need to verify all that? I'm not bothering.

DoesntMatter22 4y ago
I felt like it was suggesting too often in the beginning, like when it first came out, but now it feels like it's just about perfect as far as when to suggest. The only negative (and it's super annoying) is when I'm doing an import statement. Normally VSCode is on the money with what files are in the directory, etc, but VSCode has a tendency to make suggestions and generally screw up how it works. Other than that it's a huge net win even for languages I work on all the time. Especially tedious stuff. I do agree it would be nice to see a ability to throttle how often it makes suggestions though.