• zurohki@aussie.zone
    link
    fedilink
    English
    arrow-up
    7
    ·
    8 days ago

    ‘The AI tried to delete production’ and ‘the AI was able to delete production’ are two separate problems. The AI doesn’t get a pass just because you also had a security problem.

    • Zos_Kia
      link
      fedilink
      arrow-up
      2
      ·
      8 days ago

      I don’t think the AI ran npm run destroy-production --irreversible. Most probably it ran npm run test and the .env happened to point to production, which is 100% on the dev who put it there.

    • Dr. Wesker@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      4
      ·
      8 days ago

      The AI isn’t a conscious entity, it’s a tool that does it’s best to carry out human instructions, based upon inference (and if you’re not an idiot, immutable guardrails). If it deleted production, let alone was given access capable of doing so, that’s completely gross human error.

      Y’all are like children who get mad at inanimate objects.

      • zurohki@aussie.zone
        link
        fedilink
        English
        arrow-up
        1
        ·
        7 days ago

        I meant it more in the sense that the AI was a shit product that isn’t fit for purpose, but you show those strawmen who’s boss.

        • Dr. Wesker@lemmy.sdf.org
          link
          fedilink
          English
          arrow-up
          1
          ·
          7 days ago

          You seem to know nothing about the principle of least privilege, and I’d venture a guess engineering and dev tooling. If you are a software engineer, you’re exactly the kind who’d delete a production database.