Interesting to see the benefits and drawbacks called out.

  • chepox@sopuli.xyz
    link
    fedilink
    arrow-up
    14
    ·
    10 months ago

    I use it mostly as a help menu. Details of the function and parameter settings. Also fixing errors. I don’t use it to generate code for me though.

    • conciselyverbose@kbin.social
      link
      fedilink
      arrow-up
      22
      ·
      edit-2
      10 months ago

      Using it to generate code isn’t inherently bad (outside of copyright concerns). Especially in “stupid amount of boiler plate” languages/etc.

      But the problem is that people are lazy. They don’t bother understanding the output, making sure it does what you want it to, etc. It’s not that different than people copy pasting code from reference material. Part of the beauty of software development is that you don’t have to solve every problem someone else has already solved. But you do need to know what your code is doing and why.

      Copilot is a shortcut to code that “works” with less requirement to know what’s happening.

      • evatronic@lemm.ee
        link
        fedilink
        English
        arrow-up
        8
        ·
        10 months ago

        I thought we solved the boilerplate issue with templates and snippets like 30 years ago.

    • Landless2029@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      10 months ago

      It’s awesome for debugging for me.

      Also helped me a few times with recursive logic.

      As with any AI solution it’s “garbage in. Garbage out.”

      Write your code normally. Then ask to generate comments? Add logging? Any tips for improvements?

      You have to already know how to code so you know what to ignore.

    • linearchaos@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      10 months ago

      If I don’t use copilot to give me a piece of best practice code, I’m probably going to go and find it with a search engine.

      Obviously I’m not going to do it for every little thing but if I’m going to implement a * somewhere I screw with that what, once every 5 years?I’m going to go and look how someone else did it and probably take their exact implementation and make minor modifications.

      I’m not an absolute copy and paste fiend but I don’t have the time to reinvent the wheel every time I want to do something. For the most part it’s faster to go and grab crowd vetted code from someone that it is to go back through my own stuff and source my own implementation in the last project. Hell, and a lot of cases there might even be a better implementation than I used the last time I borrowed it from someone else.