• CorrectAlias@piefed.blahaj.zone
    link
    fedilink
    English
    arrow-up
    42
    ·
    6 hours ago

    Be careful not to introduce security vulnerabilities such as command injection, XSS, SQL injection, and other OWASP top 10 vulnerabilities. If you notice that you wrote insecure code, immediately fix it.

    Lmao. I’m sure that will solve the problem of it writing insecure slop code.

    • filcuk@lemmy.zip
      link
      fedilink
      English
      arrow-up
      17
      ·
      4 hours ago

      It doesn’t fix it, but as stupid as it looks, it should actually improve the chances.
      If you’ve seen how the reasoning works, they basically spit out some garbage, then read it again and think whether it’s garbage enough or not.
      They do try to ‘correct their errors’, so to say.

      • underisk@lemmy.ml
        link
        fedilink
        English
        arrow-up
        7
        ·
        3 hours ago

        That’s not enabled by default afaik and it burns through way more tokens looping its output through several times. It also adds a bunch more context which will bring you that much closer to context collapse.

        • Modern_medicine_isnt@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 hour ago

          I didn’t turn it on, and I see it doing it all the time. In my case though the mistakes are often absurd. I often feel like claude is a very junior programmer that has a hard time remembering the original requirements.

        • fuzzzerd@programming.dev
          link
          fedilink
          English
          arrow-up
          3
          ·
          3 hours ago

          While true, the latest opus model has 1m token context. Which is a lot more than the previous 200k limit. Hard to fill that up with regular work, but easy if you try to oneshot a whole product.