• Catoblepas@piefed.blahaj.zone
    link
    fedilink
    English
    arrow-up
    44
    ·
    12 days ago

    though the company insists the downtime was ultimately due to human error.

    I suppose using hat on top of a hat technology “agentic” “AI” in the first place is technically a human error.

    • CompactFlax@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      39
      ·
      12 days ago

      The error was executive management pushing this AI at all costs narrative.

      The blame being placed on a low ranking human.

  • Decq@lemmy.world
    link
    fedilink
    arrow-up
    12
    ·
    12 days ago

    Their reasoning that it’s a human error is, because the user gave the AI too much permissions. So does this mean this is ultimately the fault of the ceo? Because a manager gave some employee the permission to do such a thing. And another manager that manager, etc… So by this reasoning everything is always the ceo’s fault. Let’s fire him!

  • pinball_wizard@lemmy.zip
    link
    fedilink
    arrow-up
    5
    ·
    12 days ago

    Evidence that vibe coding makes even AWS go to shit.

    And of course their answer is to plan to vibe coder better, in the future. 🤖💩

  • wyrmroot@programming.dev
    link
    fedilink
    arrow-up
    4
    ·
    12 days ago

    To be fair, if I was tasked with improving Cost Explorer my first step would also be to delete the existing product