377
Finally (programming.dev)
submitted 3 years ago* (last edited 3 years ago) by to c/programmer_humor@programming.dev
32 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 14 points 3 years ago (5 children)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 7 points 3 years ago (2 children)

    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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 7 points 3 years ago* (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 4 points 3 years 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.

  • permalink
  • fedilink
  • source
  • parent