Earlier quoted context omitted.
unit test definitely a great use of copilot.
What are you talking about? I don't know anyone who uses it for this; specifically tests are really bad if they're subtly wrong. Maybe to scaffold the test function, but the actual test if completely useless if you don't trust it. So like... generate code and have robust tests, or write robust code... but, it's really really daft to generate tests that might hallucinate some random crap (and copilot really does somet…
40% of the code GitHub Copilot users check-in is AI generated and unmodified
21–30 of 129 posts
Re: 40% of the code GitHub Copilot users check-in is AI generated and unmodified
#22Re: 40% of the code GitHub Copilot users check-in is AI generated and unmodified
#23Earlier quoted context omitted.
This is my experience as well. For longer code, Copilot introduces errors through making up variables and method names that don't actually exist on the object. These errors are very annoying but only 5% of the generated code.
I tried Copilot last month and canceled my subscription because of all the small errors in generated functions. It was more painful to debug than write it myself. Maybe I should have lowered expectations and thought of it as improved code complete. I got spoiled by copy/pasting from ChatGPT. As it stands now I'd rather pay for a subscription to have the latest ChatGPT than for Copilot.
Maybe it's just me.
Re: 40% of the code GitHub Copilot users check-in is AI generated and unmodified
#24Earlier quoted context omitted.
What are you talking about? I don't know anyone who uses it for this; specifically tests are really bad if they're subtly wrong. Maybe to scaffold the test function, but the actual test if completely useless if you don't trust it. So like... generate code and have robust tests, or write robust code... but, it's really really daft to generate tests that might hallucinate some random crap (and copilot really does somet…
Most of the time I know exactly what tests I want to write but it's annoying to write them. Copilot autocompletes, I check it and then I use it.
Being able to churn out the boilerplate for tests, which can make DRY a non-concern, is great. I just hope that if I do this, I never get sloppy, and I always review the tests.
Re: 40% of the code GitHub Copilot users check-in is AI generated and unmodified
#25Earlier quoted context omitted.
unit test definitely a great use of copilot.
What are you talking about? I don't know anyone who uses it for this; specifically tests are really bad if they're subtly wrong. Maybe to scaffold the test function, but the actual test if completely useless if you don't trust it. So like... generate code and have robust tests, or write robust code... but, it's really really daft to generate tests that might hallucinate some random crap (and copilot really does somet…
Re: 40% of the code GitHub Copilot users check-in is AI generated and unmodified
#26Re: 40% of the code GitHub Copilot users check-in is AI generated and unmodified
#27I'm not surprised. A lot of the code I'll write in a day is trivial, calling helpers, writing test scaffolding, etc. I'm still building cool things the other 60% of time, but this job as we know it comes with a lot of repetition. (esp. if you write unit tests ;-))
unit test definitely a great use of copilot.
Re: 40% of the code GitHub Copilot users check-in is AI generated and unmodified
#28But no one can read my mind! If I have to get increasingly specific in what I am telling the AI, and have to formulate my writing style in a way that keeps things very precise, I am essentially programming in another language. Albeit one where the output is uncertain and I have to check everything.
It is possible that someday it reads in an entire codebase (say, millions of lines of code), and I can describe a new API I need and it implements the entire thing. This would be quite useful.
Re: 40% of the code GitHub Copilot users check-in is AI generated and unmodified
#29Earlier quoted context omitted.
What are you talking about? I don't know anyone who uses it for this; specifically tests are really bad if they're subtly wrong. Maybe to scaffold the test function, but the actual test if completely useless if you don't trust it. So like... generate code and have robust tests, or write robust code... but, it's really really daft to generate tests that might hallucinate some random crap (and copilot really does somet…
In my case about 50% of the test code is just boilerplate, so I usually type the test name and generate the rest. Most of the time I have to rewrite the actual test logic (although very trivial tests are sometimes correct), but I probably keep more than 40% if we're talking tests specifically.
Why not replace it with a function call?
Re: 40% of the code GitHub Copilot users check-in is AI generated and unmodified
#30for me it’s a fancy autocomplete at its worst! it’s a handy tool to cut down on repetitive tasks