News for hackers. Stuff that matters.

A comment on Don't encode POST bodies like GitHub Copilot, use URLSearchParams. Parent comment

Re:Don't encode POST bodies like GitHub Copilot, use URLSear... by TeMPOraL on Thursday July 01, 2021 @08:52AM (#27698587)
Spotting bugs in code review is already hard when the code you're reviewing has been written by a human. In this case, at least you can rely on your knowledge of the co-worker who wrote it - over time, you learn the kind of experience they have, the kind of mistakes they make.

Spotting bugs in code that has been generated by a GPT-3 derivative, with all the subtle mistakes that implies, is going to be even harder.

[ Parent | on HN ]
Re:Don't encode POST bodies like GitHub Copilot, use URLSear... by stackbutterflow on Thursday July 01, 2021 @10:40AM (#27699468)
In the end we need to tag each piece of code written by copilot. Doing a code review on a piece of code written by a human and on another one generated by copilot is going to be a very different experience. I would be way more wary of a PR containing copilot generated code. Turns out copilot will be a productivity killer.
[ Parent | on HN ]
Re:Don't encode POST bodies like GitHub Copilot, use URLSear... by aeorgnoieang on Thursday July 01, 2021 @04:34PM (#27704428)
> Spotting bugs in code that has been generated by a GPT-3 derivative, with all the subtle mistakes that implies, is going to be even harder.

I'm kind of skeptical! I think your claim is reasonable tho so maybe I'm more skeptical of your confidence?

I'd love to read a follow-up from you after you tried using Copilot for an extended period; even (or maybe especially) if it's as bad, or worse, than you expect!

[ Parent | on HN ]