• @[email protected]
    link
    fedilink
    English
    89 months ago

    Manager (34) impregnated a delivery driver (16/17) and ran away to Tennessee because he couldn’t be prosecuted for it there.

  • stinerman
    link
    fedilink
    English
    539 months ago

    There was a guy who was in tech support who talked to a customer about who was hot or not in the company. It was actually the customer who started the conversation, but the rep ran with it and used all kinds of unprofessional and disparaging language when describing his female co-workers.

    That call happened to have a supervisor listening in, so he was fired immediately after he got off the call. The thing is found out who called in, and the women on the team had to assist him when he called for support.

  • @[email protected]
    link
    fedilink
    449 months ago

    Someone got really drunk and was in the bathroom willing to take all comers at a work function.

    It was a shame, I liked working with them.

  • @[email protected]
    link
    fedilink
    689 months ago

    Working on a boat. We got a new shipmate who had worked there on previous seasons, most of us didn’t know him but he was good friends with another member of the crew. The day he got in the two of them spent the night catching up and getting absolutely trashed. Night ended with new guy stumbling in to the cook’s cabin and pissing right on the cook while he was sleeping. New guy was fired that morning without having worked a single day.

    • @[email protected]
      link
      fedilink
      109 months ago

      Hopeful ship was at shore still at the time? Would suck to be fired while out at sea. Awkward ride back.

      • @[email protected]
        link
        fedilink
        4
        edit-2
        9 months ago

        We were in Puerto Rico for our winter maintenance period, just starting to bring on crew for the sailing season. I’ve never worked on a boat where people drink underway and I don’t think I’d want to.

        On boats you usually don’t get told you’re fired until you reach port.

  • @[email protected]
    link
    fedilink
    English
    92
    edit-2
    9 months ago

    A guy in our data center couldn’t figure out who owned a particular machine that he needed to work on. So his solution to figure it out was to let them come to him. He went and pulled out the network cable and waited. He was escorted out a little while later. The moral of the story is don’t go disabling production machines on purpose.

    • @[email protected]
      link
      fedilink
      349 months ago

      Where I worked we had a very important time sensitive project. The server had to do a lot of calculations on a terrain dataset that covered the entire planet.

      The server had a huge amount of RAM and each calculation block took about a week. It could not be saved until the end of the calculation and only that server had the RAM to do the work. So if it went down we could lose almost a weeks work.

      Project was due in 6 months and calculation time was estimated to be about 5 1/2 months. So we couldn’t afford any interruptions.

      We had bought a huge UPS meant for a whole server rack. For this one server. It could keep the server up for three days. That way even if wet lost power over the weekend it would keep going and we would have time to buy a generator.

      One Friday afternoon the building losses power and I go check on the server room. Sure enough the big UPS with a sign saying only for project xyz has a bunch of other servers plugged into it.

      I quickly unplug all but ours. I tell my boss and we go home at 5. Latter that day the power comes back on.

      On Monday there are a ton of departments bitching that they came in an their servers were unplugged. Lots of people wanted me fired. My boss backed me and nothing happened but it was stressful.

      • @[email protected]
        link
        fedilink
        English
        49 months ago

        At a startup a long time ago, I was working on the weekend and brought my 3 year old with me. We had a customer coming in next week and this one machine was 5 days into a 7 day model build.

        We had to go into that office to help someone with something unrelated. The little shit saw the blinking light and headed straight for the button.

        On this computer (HP 710), it didn’t shut off until you released the button. He actually was just pressing it but got spooked when I tried to get to it.

        The next day our CEO told the guys that built that app that it had to be made so it could recover from crashes and restart from where it left off.

      • @[email protected]
        link
        fedilink
        29
        edit-2
        9 months ago

        I’d be super gluing those plastic toddler plug covers all over that thing.

        fuck those other departments.

    • @[email protected]
      link
      fedilink
      779 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.

          • @[email protected]
            link
            fedilink
            109 months ago

            I don’t understand how that is even possible.
            Are there no logs? No documentation? Does everyone share an admin user with full rights?
            I mean, there has to be a way to find out who accessed the machine last time.

            • @[email protected]
              link
              fedilink
              69 months ago

              company a gets bought by company b. company b fires 50% of company a.

              even a scream test won’t get you answers because nobody is around that could complain nor know where the docs are.

            • @[email protected]
              link
              fedilink
              15
              edit-2
              9 months ago

              You’d be surprised with inheriting tech debt. Quite often there’s no documentation, the last person to log in to the system is an admin that quit 3 years ago, but it doesn’t much matter because that’s only for a direct console login which normal users don’t do when accessing the application. With tribal knowledge gone and no documentation, only when you pull the network for a bit do you discover that there was this one random script running on it that was responsible for loading up all the needed data in the current system, when 9 of the other 10 times those scripts were no longer needed.

              In a perfect world you’d have documentation, architecture and data flow diagrams for everything, but “ain’t nobody got time for that” and it doesn’t happen.

              • @[email protected]
                link
                fedilink
                59 months ago

                Had that the other way around recently. A docker container failed to come back up after I had updated the host OS.
                Was about ready to restore the snapshot, when I looked further back in the logs on a hunch.
                Turns out that container hadn’t worked before the update either. The software’s developer is long gone, and no one could tell me what it was supposedly doing.

            • @[email protected]
              link
              fedilink
              19 months ago

              You’d be surprised. I had some security devices that I was actively using get shut down simply because some paperwork didn’t get filled out properly and the data center team claimed they had no documentation on them.

          • @[email protected]
            link
            fedilink
            English
            19 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.

      • @[email protected]
        link
        fedilink
        English
        469 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.

          • @[email protected]
            link
            fedilink
            English
            109 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?

    • @[email protected]
      link
      fedilink
      349 months ago

      Yeah, I’ve done that before – after asking literally everyone in IT, plus our external consultants, and getting the go-ahead from my team lead and the head of IT.

  • @[email protected]
    link
    fedilink
    59
    edit-2
    9 months ago

    A guy on my team was absolutely convinced the external monitors he had were 1080p and not 1680*1050 resolution, and that everyone else using 1680*1050 were just wrong. He got into an argument with IT service desk over HDMI cables, which he wanted to prove himself correct (since everyone else were supposedly chumps for accepting the tyranny of having to use DVI cables for their monitors, thus forcing them to use the lower resolution). The argument escalated and well, he kind of just disappeared after that and never came back.

    The IT service desk folks were already touchy about their HDMI cables since people were apparently stealing them for use in the meeting rooms.

    Pity, I liked him but that was kind of unhinged. Besides, the monitors’ native res was definitely 1680*1050 lol.

  • @[email protected]
    link
    fedilink
    English
    469 months ago

    Help desk guy caught jerking off at his desk by a female employee, which he had apparently been doing for a while without a whole lot of cleanup, further investigation uncovered.

    His keyboard, mouse, desk, floor mat, and chair were disposed of as hazmat. Monitor and PC were e-cycled.

    • Drusas
      link
      fedilink
      49 months ago

      I used to work tech support for a company that made a product which involved sharing live or recorded videos. We would use the same instance for testing and troubleshooting, which occasionally involved broadcasting live videos.

      One morning, I signed on to look for something or other, and I saw that one of my co-workers (who was working from home) had a live feed. His camera was pointed straight at his crotch and he was going at it quite vigorously. I deleted the feed and I don’t know if he ever even knew what happened.

      • @[email protected]
        link
        fedilink
        English
        29 months ago

        Honestly I’d probably do the same. He’s at home, and I don’t need that drama in my work life.

        • Drusas
          link
          fedilink
          19 months ago

          Didn’t need a perfectly good coworker fired because he didn’t realize his camera was on.

          • @[email protected]
            link
            fedilink
            English
            29 months ago

            Stories like that are why my webcam shutter is closed AND it’s unplugged until I need it.

            Ain’t nobody seeing me unless I go through the effort to hook it up.

  • @[email protected]
    link
    fedilink
    English
    89
    edit-2
    9 months ago

    Guy in my department strolls into my office and says, “Welp, this is probably my last day working here.” I asked him why he would say that. He sits down and shoves his phone across the desk toward me. I start reading and it’s an email from him to the CEO complaining that our boss is, in so many words, a complete fucking moron.

    I finished reading and was just like, “Yeah, you shouldn’t have done that.” I mean, he wasn’t wrong. I agreed with basically everything in his email. He was also right about it being his last day working there because he was fired that afternoon.

    • @[email protected]
      link
      fedilink
      319 months ago

      We had a guy that would email the CEO with audio or video of him singing or something. Good dude. Sold people eggs every week from his hens. Got fired for actual bullshit his lead should’ve been canned for.

    • @[email protected]
      link
      fedilink
      10
      edit-2
      9 months ago

      Hmmmmm. Been thinking about starting a youtube channel. Maybe ballads to the CEO could be the theme. I wonder how long before I get called in by hr.

  • @[email protected]
    link
    fedilink
    English
    409 months ago

    I’ve worked with a lot of good and a lot of bad surgeons, but even the bad ones aren’t usually dangerous bad, but like slow af, sub-optimal but passable outcomes, shit like that.

    I’ve worked with ONE who was just absolute shit at his job… and his incompetence got at least one patient killed.

    He got axed pretty quick… hopefully his license was revoked and he got charged with murder, but I never got any details of post-firing.

      • @[email protected]
        link
        fedilink
        English
        189 months ago

        No, he never got any media attention that I’m aware of. My concern is that he’s just hopping from hospital to hospital - hiring on, fucking up, killing someone, getting fired, hiring on, fucking up, killing someone, etc.

        Hospitals are pretty protective of their reputation and their doctors; and death is a thing that can happen in surgery so it be swept off as a “Oh well, patient signed off on the risks; and oh hey, this Dr said some mean things to our staff, so let’s fire him for that and hope we don’t make national headlines…”

        • ShaunaTheDead
          link
          fedilink
          39 months ago

          That’s exactly what happened with Dr Death and why he wasn’t caught for such a long time.

          • @[email protected]
            link
            fedilink
            English
            19 months ago

            Oh, well shit. Dr Death was before this shit, but it sounds like basically Dr Death 2.0.

            …kinda makes me wonder how common this is.

    • Drusas
      link
      fedilink
      29 months ago

      Not that I’ve had a ton of surgeries, but I’ve had a couple, and anytime I go under, I’m desperately hoping that my surgeon wasn’t a C student and has the calmest of hands.

      • @[email protected]
        link
        fedilink
        English
        39 months ago

        Most docs have some kind of internet presence nowadays, so definitely look them up. Also in the later preop stages when you talk to your OR nurse, look your nurse in the eye and just straight up ask “Would you be comfortable with this doctor operating on you?” They won’t be actually allowed to talk shit on their surgeon, but the second of panicked silence as they try to come up with some kind of non-answer without blatantly lying will tell you everything you need to know.

        This might be like 30 mins before your surgery - you have the right to refuse up until you go unconscious. It’ll feel dirty, but those standards exist for a reason.

        • Drusas
          link
          fedilink
          29 months ago

          That’s a good suggestion about talking to the nurse, thank you.

    • @[email protected]
      link
      fedilink
      19 months ago

      Curious how common the truly bad ones are. I’d assume quite uncommon between licensing, hospital hiring, chart data analysis at scale, etc., but…

      Counting down the days to a relatively minor surgery I need. No real concerns, I’ve met the lead surgeon a few times, but plenty of unknown humans are part of the process too.

  • @[email protected]
    link
    fedilink
    389 months ago

    On a virtual meeting a guy unknowingly had his mic on and shouted to his kid “N…r sit your ass down!”

            • @[email protected]
              link
              fedilink
              English
              209 months ago

              If the guy was talking to his kid like that, I’m going to go out on a limb here and assume it was a black guy yelling at his kid, and not being a racist. Maybe it was a white guy, but that doesn’t sound like something a white guy would yell at their kid, even a racist.

              • @[email protected]
                link
                fedilink
                39 months ago

                Not all black people think that using the n-word is ok and many will tell you that no matter who is using it, the word has a racist undertone.

                When you work for an employer that makes it a point to embrace multiculturalism it’s not the kind of language you can use while you’re working.

                • Drusas
                  link
                  fedilink
                  29 months ago

                  While what you say is true, it doesn’t really refute the comment you’re replying to. It could have been a black, non-racist employee, but that doesn’t mean it’s okay to use offensive language in the workplace.

            • @[email protected]
              link
              fedilink
              119 months ago

              “clean work culture” = “It’s not enough when a worker does their job, they also have to adjust their behavior to their employer’s wishes, both at work and in their free time.”

    • @[email protected]
      link
      fedilink
      29 months ago

      Company has low-key software trainers - a ton of information to convey, but they mostly embrace and gently corral the inevitable side convos you get in a Teams room of thirty very confused people.

      Some of us were more vocal than others and a handful were less pleasant. During a brief silence, as a woman is about to ask a valid question, we ALL hear,

      “Oh, there’s Jennifer, running her fat fucking mouth again! (Pause) (gasp from speaker)”

      Guy wasn’t getting it anyway, but he didn’t last the rest of the morning.

      There were 29 of us in that room, two years ago. Now there are six of us remaining. Mouthy guy above is the only one I know left involuntarily.

  • Angry_Autist (he/him)
    link
    fedilink
    449 months ago

    Some fuckwad printed out several hundred illegal pictures in the middle of the day in a place accessible to everyone and with high foot traffic.

    Needless to say he was walked out by the cops.

    • @[email protected]
      link
      fedilink
      30
      edit-2
      9 months ago

      There is so much stupid shit that you can get away with in the military, I have never understood why anyone would even get close to breaking the fraternization rules. They literally give you a copy of the rulebook in boot camp! Did no one read the damn thing?

      I was a Nuke though, so up to my neck in daily fires to put out. No time for a social life.

  • @[email protected]
    link
    fedilink
    679 months ago

    Mike would walk into random meetings that he didn’t belong in, lay his head on the table, and knock out. Snored loud as fuck. He did this in my meetings alone at least three times a week.

    He’d be found sleeping in the driver seat of his car about once a day too, clocking hours.

    I saw the dude sneak up on a lot of people and assault them. Smack mens asses, rub women’s shoulders, he put this catholic nerd in a chokehold and whispered “security can’t help you here, n****” and then let him go.

    He’d talk about how sick work from home was, how he’d just play NBA2K and Tekken all day, work on his car, sleep, and get paid.

    Homie worked with us for like 3 or 4 months before he got fired. When he left, I got assigned his work. He had one ticket. It was three months old, and it was to update some software on our platform from vX to vX+1. It took me three minutes.

    Dude was reading comic books at his desk the entire time he was there. He was really living the dream for a minute, I heard after he got fired that he moved from computers to car mechanic.

    • @[email protected]
      link
      fedilink
      English
      24
      edit-2
      9 months ago

      How did that take more than 3 months? Surely he should have been noticed within a week…

      • @[email protected]
        link
        fedilink
        199 months ago

        My company is small enough that it doesn’t legally need HR.

        Nobody to report him to except the company owners who didn’t care for a while

      • @[email protected]
        link
        fedilink
        379 months ago

        Guy was having fun being a menace, and making 6-figures.

        He would also record/take pictures of girls he’d meet online, and show off their nudes to people at work. And complain about paying child support. Gross ass dude.

        He was hired on the recommendation of an already existing (seemingly normal) employee. Once mike got fired, his recommender immediately ““quit”” before they could also get fired

  • @[email protected]
    link
    fedilink
    English
    639 months ago

    Unhinged entry level employee screaming and swearing and threatening the CFO and spit in her coffee mug.

    An email went out to the whole company telling us not to let him in the building before he even got back to his desk to be fired. This is a software company, not exactly the type of place that has armed guards, but the (ex-military) information security dude set up in the area packing for a few weeks after that.