• blackjam_alex@lemmy.world
    link
    fedilink
    English
    arrow-up
    61
    arrow-down
    2
    ·
    4 days ago

    My experience with ChatGPT goes like this:

    • Write me a block of code that makes x thing
    • Certainly, here’s your code
    • Me: This is wrong.
    • You’re right, this is the correct version
    • Me: This is wrong again.
    • You’re right, this is the correct version
    • Me: Wrong again, you piece of junk.
    • I’m sorry, this is the correct version.
    • (even more useless code) … and so on.
    • saltesc@lemmy.world
      link
      fedilink
      English
      arrow-up
      35
      ·
      edit-2
      4 days ago

      All the while it gets further and further from the requirements. So you open five more conversations, give them the same prompt, and try pick which one is least wrong.

      All the while realising you did this to save time but at this point coding from scratch would have been faster.

    • sugar_in_your_tea@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      28
      ·
      edit-2
      4 days ago

      I interviewed someone who used AI (CoPilot, I think), and while it somewhat worked, it gave the wrong implementation of a basic algorithm. We pointed out the mistake, the developer fixed it (we had to provide the basic algorithm, which was fine), and then they refactored and AI spat out the same mistake, which the developer again didn’t notice.

      AI is fine if you know what you’re doing and can correct the mistakes it makes (i.e. use it as fancy code completion), but you really do need to know what you’re doing. I recommend new developers avoid AI like the plague until they can use it to cut out the mundane stuff instead of filling in their knowledge gaps. It’ll do a decent job at certain prompts (i.e. generate me a function/class that…), but you’re going to need to go through line-by-line and make sure it’s actually doing the right thing. I find writing code to be much faster than reading and correcting code so I don’t bother w/ AI, but YMMV.

      An area where it’s probably ideal is finding stuff in documentation. Some projects are huge and their search sucks, so being able to say, “find the docs for a function in library X that does…” I know what I want, I just may not remember the name or the module, and I certainly don’t remember the argument order.

      • 9488fcea02a9@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        17
        ·
        4 days ago

        AI is fine if you know what you’re doing and can correct the mistakes it makes (i.e. use it as fancy code completion)

        I’m not a developer and i havent touched code for over 10 yrs, but when i heard about my company pushing AI tools on the devs, i thought exactly what you said. It should be a tool for experienced devs who already know what they’re doing…

        Lo and behold they did the opposite… They fired all the senior people and pushed AI on the interns and new grads… and then expected AI to suddenly make the jr devs work like the expensive Sr devs they just fired…

        Wtf

      • slaacaa@lemmy.world
        link
        fedilink
        English
        arrow-up
        7
        ·
        3 days ago

        AI is like having an intern you can delegate to. If you give it a simple enough task with clear direction, it can come up with something useful, but you need to check.