• mac@infosec.pub
    link
    fedilink
    arrow-up
    19
    ·
    9 months ago

    Pretty much this, it’s the one use case for copilot, I know what I want to type anyway and copilot is usually close enough that 2 edits is faster than typing the whole thing and better for rsi.

    • Kalothar@lemmy.ca
      link
      fedilink
      arrow-up
      7
      arrow-down
      1
      ·
      9 months ago

      Basically the work flow has changed from:

      Find a framework that I need to integrate for whatever reason. Go to GumboChumbo.io read the docs.

      Write some code based off of what’s in the doc, test the thing, read error message, read docs, ad new thing, but wall for obscure reason, spend thirty minutes looking through similar issues via Google-fu and then find an obscure comment from 6 years ago, That some how fixes this current issue. Implement it, get it working and then customize it.

      Now it just streamlines finding these solutions.

      • mac@infosec.pub
        link
        fedilink
        arrow-up
        3
        ·
        edit-2
        9 months ago

        Yeah it’s definitely a lot quicker than searching through 15 articles and stack overflow posts sometimes. Except for with regex and the sed command, the bastard thing kept messing that up

    • poinck@lemm.ee
      link
      fedilink
      arrow-up
      2
      ·
      9 months ago

      But sometimes Copilot just uses too much words to present the answer, so I use ChatGPT which can be personalized.

      (Maybe it is possible with Copilot, too, maybe I have to ask how to do it)

      • mac@infosec.pub
        link
        fedilink
        arrow-up
        3
        ·
        9 months ago

        I find the opposite, chatgpt (free version at least) gives all the explanation and stuff then a code block, copilot (not Microsoft the GitHub one) just prints the boilerplate directly in the editor then you press tab to accept.