Conversation

Notices

1. Embed this notice
   Itamar Turner-Trauring (itamarst@hachyderm.io)'s status on Friday, 10-Nov-2023 20:07:11 JST Itamar Turner-Trauring

   Thinking about it some more, the fundamental flaw with CoPilot is that the goal is to make it faster and easier to generate code.

   As a programmer, you don't want to generate code.

   You want to solve problems, and the less code involved the better. I don't want tools that will generate repetitive code, I want less repetition.

   https://github.blog/2022-09-07-research-quantifying-github-copilots-impact-on-developer-productivity-and-happiness/ shows the problem. "Less mental effort on repetitive tasks", sure, but you should be trying to _prevent_ the repetition, not do more of it.

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Friday, 10-Nov-2023 20:09:54 JST Haelwenn /элвэн/ :triskell:

     in reply to
     @itamarst It's rather weird, an HTTP server, assuming NodeJS as other JS environments typically don't give any TCP APIs, is part of the standard library: https://nodejs.org/api/http.html
     
     Where they not able to read documentation?
   • Embed this notice
     Itamar Turner-Trauring (itamarst@hachyderm.io)'s status on Friday, 10-Nov-2023 20:09:55 JST Itamar Turner-Trauring

     in reply to

     Like, they do an experiment, and it's faster to write an HTTP server with JavaScript with CoPilot. Great, but why would you do that? Why not using an existing server?

     (To be fair, when I was writing Go I would have been happier if I had a tool like CoPilot. But that feels like a flaw in Go; consider how Rust does the exact same kind of error handling, just vastly better.)