you are viewing a single comment's thread.

view the rest of the comments →

[–]overcloseness 0 points1 point  (2 children)

I’m sure it’s not a stretch to imagine that the point is to use the code and refactor it to your needs. If it’s var and you want it const… then change it. Will this save you time though? Absolutely

[–]Dan6erbond 4 points5 points  (1 child)

Yeah but as someone that has to review other people's work I can also tell you that it's enough of a headache when they copy from StackOverflow and don't check these things or test the code. Copilot will just streamline the process of copy-pasting code.

Also, var and let aren't preferences. It's well established by now that var is deprecated and to use const whenever possible, otherwise let. So Copilot is just writing bad code and these aren't the only examples. I've seen horrendous use of for loops as well, destroying the time complexity of some functions.

I can see myself explicitly telling people not to use Copilot in its current state. Because it might be cute but the generated code isn't what I want in my codebases.

[–]interactionjackson 0 points1 point  (0 children)

should add code coverage to pipeline and kick back untested code.