• FaceDeer@kbin.social
    link
    fedilink
    arrow-up
    14
    arrow-down
    1
    ·
    1 year ago

    Often when I tell ChatGPT what error its code produced it will immediately figure out what the bug was and fix it.

    • lackthought@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      7
      ·
      1 year ago

      interacting with chatgpt is a learned skill

      i’ve used it several times and while the initial code may have some issues you can get them cleared up with a few direct follow ups

      • FaceDeer@kbin.social
        link
        fedilink
        arrow-up
        7
        ·
        edit-2
        1 year ago

        I recall reading a while back of one person’s strategy, whenever ChatGPT generates code for him he immediately tells ChatGPT “there’s a bug in that code” (without checking or specifying). It’ll often find one.

        Another approach I’ve heard of is to tell ChatGPT that it’s supposed to roleplay two roles when generating code, a programmer and a code reviewer. The code reviewer tidies up the initial code and fixes bugs.

        Since often ChatGPT’s code works fine for me I don’t usually bother with these steps initially, since I’m usually just wanting a quick and dirty script for a one-off task the quality doesn’t matter much in my case.

        • jcg@halubilo.social
          link
          fedilink
          arrow-up
          3
          ·
          1 year ago

          And you know what you call changing words around to get a computer to do what you want? That’s programming, baby! We are programming programmers!

    • philm@programming.dev
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      Yeah, this is the way how to interact with it. It makes sense as well, because it’s only predicting the next word based on the previous words, so it had can in hindsight find a lot more stuff and in general be smarter about it.

    • orca@orcas.enjoying.yachts
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      1 year ago

      I do this with TypeScript error codes. It’s great at breaking down the problem. I never just copy paste code from it and I don’t think anyone should do that anyway.