• over_clox@lemmy.world
    link
    fedilink
    arrow-up
    29
    arrow-down
    3
    ·
    2 days ago

    Now where does this thought come from?

    Do you not know what a computer is? It’s literally a digital logical accountant! Yeah yeah, we should probably blame the programmers and engineers instead when shit goes sideways, but now I think we need to also hold CEOs accountable when they decide to inject faulty AI into mission critical systems…

    https://lemmy.dbzer0.com/post/55990956

    • henfredemars@infosec.pub
      link
      fedilink
      English
      arrow-up
      17
      ·
      2 days ago

      There’s a reason why license agreements often stay there there are no warranties express or implied, no guarantees, and no fitness for any particular purpose.

    • mogranja@lemmy.world
      link
      fedilink
      arrow-up
      8
      ·
      2 days ago

      If a building collapses. You blame the people who built the walls and poured the concrete, or the ones who chose the materials and approved the project?

      In any case, often programmers and engineers retain no rights to the software they worked on. So whoever profits from the software should also shoulder the blame.

      • over_clox@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        2 days ago

        Those in charge, that approve the continued use of proven faulty software, should take all the blame, after significant faults have been proven anyways.

        I mean you have a point, but still, 1+2+3≠15, and a bag of Doritos is not a gun. When AI fucks up this badly, the real guilty parties

        (my AI keyboard wanted to replace guilty with gullible BTW, and I’m using the FUTO keyboard no less),

        the real guilty parties are the ones in charge that allow such proven faulty systems to continue running for mission critical systems.

        Like fuck, a bag of Doritos is not a fucking gun!