• ramble81@lemm.ee
    link
    fedilink
    arrow-up
    93
    ·
    2 months ago

    Honestly we do that when we ask and no one speaks up. Lovingly called the “scream test” as we wait to see who screams.

    • FigMcLargeHuge@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      59
      arrow-down
      2
      ·
      2 months ago

      I guess it depends on where you work. This was a large datacenter for a very large health insurance company. They made it a point later that day to remind people that it was a fireable offense to mess with production machines like that on purpose. And evidently the service he disabled was critical enough that it didn’t take long for the hammer to come down. There were plenty of ways to find out who owned the machine, he just chose the easiest and got fired on the spot for it.

        • FigMcLargeHuge@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          18
          ·
          2 months ago

          Well I am not him, so I can’t tell you whether or not he actually “could” have figured it out. The options to figure it out did exist, but he chose not to use them giving it the appearance that he “couldn’t”. Are you this much fun at parties?

        • gravitas_deficiency@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 months ago

          I read that as “lazy to the point of unprofessionalism”. I’m super lazy too, but it just means I try to automate the absolute shit out of everything I do to the greatest degree possible.