• not_woody_shaw@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    ·
    13 hours ago

    It can complete coding tasks, but not well AND unsupervised. To get it to do something well I need to tell it what it did wrong over 4 or 5 iterations.

    • Repple (she/her)@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      5 hours ago

      This is close to my experience for a lot of tasks, but unless I’m working in a tech stack I’m unfamiliar with, I find doing it myself leads to not just better results, but faster, too. Problem is it makes you have to work harder to learn new areas, and management thinks it’s faster for everything and

      • not_woody_shaw@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        4 hours ago

        I think it’s still faster for a lot of things. If you have several different ideas for how to approach a problem the robot can POC them very quickly to help you decide which to use. And while doing that it’ll probably mention something that’ll give you ideas for another couple approaches. So you can come up with an optimal solution in about the same time as it’d take to clack out a single POC by hand.

        • Repple (she/her)@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          4 hours ago

          Yeah, I was thinking about production code when I wrote that. Usually I can get something working faster that way, and for tests it can speed things up, too. But the code is so terrible in general

          Edit: production isn’t exactly what I was thinking. Just like. Up to some standards above just working