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 wyuenho on Thursday July 01, 2021 @08:02AM (#27698255)
The problem is with Copilot, or over-relying on it for its purported convenience, bad devs will have a harder time becoming good devs. Discovering what code to write and what their exact effects are is a major part of the journey to becoming good dev. If humans aren't going thru this process, I very much doubt they'll be able to quality control the code Copilot dumps in until later in the cycle. Doing things the hard way is essential for being a good dev.
[ Parent | on HN ]
Re:Don't encode POST bodies like GitHub Copilot, use URLSear... by emodendroket on Thursday July 01, 2021 @08:21AM (#27698361)
I've heard this same line for using IDEs for years. Everyone else is welcome to stick with Ed if they like. I'm going to use the tools that are available to me to make my job easier.
[ Parent | on HN ]
Re:Don't encode POST bodies like GitHub Copilot, use URLSear... by auggierose on Thursday July 01, 2021 @08:42AM (#27698527)
If you don't understand the difference between Idea IntelliJ, which I loved as soon as it came out, and Github Copilot, then you are exactly the reason why I am frightened.
[ Parent | on HN ]
Re:Don't encode POST bodies like GitHub Copilot, use URLSear... by emodendroket on Thursday July 01, 2021 @08:51AM (#27698581)
IntelliJ and friends make a lot of suggestions, which aren't always good to blindly accept. It's not exactly the same but it's in the same universe of machine-assisted work that still requires human direction.
[ Parent | on HN ]
Re:Don't encode POST bodies like GitHub Copilot, use URLSear... by pyrale on Thursday July 01, 2021 @09:11AM (#27698725)
There's a pretty big difference between asking a permission and going on unless that same permission is denied.

There's also a large difference in scope between the kind of suggestions a linter gives and what copilot does. Linter usually works around the syntax for equivalent semantics, while copilot tries to infer semantics.

[ Parent | on HN ]
Re:Don't encode POST bodies like GitHub Copilot, use URLSear... by emodendroket on Thursday July 01, 2021 @09:24AM (#27698793)
IntelliJ does a lot of the latter with templates.
[ Parent | on HN ]
Re:Don't encode POST bodies like GitHub Copilot, use URLSear... by marcosdumay on Thursday July 01, 2021 @12:39PM (#27701060)
Code templates are the top reason why I avoid IDEs. You just start writing something and the IDE will insert a block of code there, with no indication of where it ends, and catching you off guard if you are focused on something other than data input.

The fact that there are so many people that like them that all the IDEs have the feature on by default with the off switches scattered all over their configuration so you can't turn them off is scary.

[ Parent | on HN ]
Re:Don't encode POST bodies like GitHub Copilot, use URLSear... by emodendroket on Thursday July 01, 2021 @03:34PM (#27703528)
I'm not sure what's scary about it. I find them useful. And I find the behavior is pretty predictable with experience.
[ Parent | on HN ]
Re:Don't encode POST bodies like GitHub Copilot, use URLSear... by IncRnd on Thursday July 01, 2021 @08:54AM (#27698602)
When you work for a company that forbids copilot and blocks its traffic from the network, you'll find that your dependence on tools to create your code has held you back.
[ Parent | on HN ]
Re:Don't encode POST bodies like GitHub Copilot, use URLSear... by emodendroket on Thursday July 01, 2021 @08:59AM (#27698636)
Heard that one before too. I have to work without the IDE for interviews and it's not a big deal. It's just slower and less efficient.
[ Parent | on HN ]