• KrummsHairyBalls@lemmy.ca
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    1 year ago

    I messed around with it back when it was apparently better than it is now, and it sucked ass. Fed me outdated info, broken code, and overall was a nightmare.

    Tried it recently real quick because I was converting my code, and I didn't want to dig in the documentation, and the info ChatGPT spit out was 100% false. Not even broken, just wrong.

    • Terrasque@infosec.pub
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      1 year ago

      It can be surprisingly helpful. I needed a small program to change between three "states", two separate programs that use the gpu and can't run at the same time that I run on a server, and an "idle" state where none of them are running. And a simple web ui to check and change state.

      This was the conversation: https://chat.openai.com/share/661322bc-2bd2-4608-9c7f-ec6d9f488601

      Note that it did mess up the transitions code a bit, but it was easy to fix after a brief look at the documentation. However, the http page worked 100% straight off the bat, and the flask code and running of the commands worked perfectly. It's not a big thing, but a lot of "boilerplate" code and double checking docs was avoided. And this is the free tier.

    • waylaidwanderer@lemmy.ca
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      I feed it the relevant documentation first. It has large enough context size to handle it. But even that's unnecessary as long as you're not using a niche library.