Asklemmy

I spent a decade working in insolvency.

When we were going into a business that had failed the question was "Are the idiots, criminals or both?"

One highlight:

A boat sales / marine business goes bust. When we arrive with the paper work and seize the place there are about a dozen new boats on the lot worth several million. We change the locks on the gates.

Arrive the next day, the gates have been busted open and several million in boats are now missing. We look up the addresses of the owners (one of them lives on acreage) and drive to their property...from the road we can see the boats stashed there. Really smart guys.

So we call the police. Someone inside notices use there and decides to flee with one of the boats, it is huge but they think they can get away.

We then have the slowest car chase in history as we calmly follow this guy towing a boat on a trailer down the road while talking to the cops to meet us.

I worked at a sandwich shop and had given my two weeks notice a few days earlier. My manager came to me and asked me to clean up the bathroom...alright. I could smell it before I even opened the door.

I told my manager I'd clean it if he'd still give me the employee discount after I was gone. "Done". That's when I knew it was really bad.

When I opened the door I discovered someone had ass-blasted the bathroom. I'm not talking about blowing up the toilet, they did that too, but they had dropped their drawers and point-blank diarhea shotgunned the pipes under the sink.

My manager didn't honor the employee discount after I was gone, either.

I used to work at a car dealership. One day I had to use a bay in a different building because my usual workplace was occupied. The other building had a lift that I hadn't used before.

Anyways, I drove the car onto the lift, got out and placed the arms of the lift under the jacking points like I had done a thousand times before. I raised the lift a little and checked if the placement was still correct. It looked good, so I raised the car to a medium height. When I looked again, I realized that this lift had a central platform that was also raised and was set about 20 centimeters higher than the four arms that usually lift the car.

This 90.000 Euro SUV was basically balancing on a 180x50cm piece of metal right in the center. I managed to lower it down safely but my pulse goes up just thinking about that day.

An isolated shingle spit nature reserve. We'd lost mains power in a storm some while back and were running on a generator. Fuel deliveries were hard to arrange. We'd finally got one. We were pretty much running on fumes and another storm was coming in. We really needed this delivery.

To collect the fuel, I had to take the Unimog along a dump track and across 5 miles of loose shingle - including one low causeway stretch through a lagoon that was prone to wash out during storms. We'd rebuilt it a LOT over the years. On the way up, there was plenty of water around there, but it was still solid.

I get up to the top ok and get the tank full - 2000L of red diesel - but the wind is pretty strong by the time I have. Half way back, I drop down off the seawall and reach the causeway section. The water is just about topping over. If I don't go immediately, I won't get through at all and we will be out of fuel for days - maybe weeks. So I put my foot down and get through that section only to find that 200 meters on, another section already has washed out. Oh shit.

I back up a little but sure enough the first section has also washed through now. I now have the vehicle and a full load of fuel marooned on a short section of causeway that is slowly washing out. Oh double shit. Probably more than double. Calling it in on the radio, everyone else agrees and starts preparing for a pollution incident.

In the end I find the firmest spot that I can in that short stretch and leave the Moggie there. Picking my route and my moment carefully I can get off that 'island' on foot - no hope with the truck - BUT due to the layout of the lagoons only to the seaward ridge, where the waves are now crashing over into the lagoon with alarming force. I then spend one of the longest half-hours I can remember freezing cold and drenched, scrambling yard by yard along the back side of that ridge and flattening myself and hoping each time a big wave hits.

The firm bit of causeway survived and there was no washed away Unimog or pollution in the end - and I didn't drown either - but much more by luck than judgement.

These days I am in a position where I am responsible for writing risk assessments and methods statements for procedures like this. It was another world back then.

Two nights ago I had a random meeting with the CEO, who I have a really good relationship with, added to my calendar. Thought nothing of it.

I entered the zoom call and said ‘so am I getting fired?’

The answer was yes.

Awkward silence ensued for a minute until they started telling me about the severance package.

Side note: I can try to negotiate that severance a bit right?

Sharing my story for posterity.

I used to work at a medical center for old folks with varying disabilities. It was a great job all things considered, just didn't pay very well and the scheduling was a mess.

Anyway, one day I'm cleaning tables on the dining room when I hear on my walkie talkie that one of the new people need help with a guy in the bathroom. Usually "they need help" means "something has gone awry, please unfuck the situation" and, since I was the supervisor on shift, my job frequently involved untucking a situation.

I arrive outside the bathroom door and the new employee tells me that she walked into a situation that she wasn't prepared for. I figured it was some poop, or the guy fell asleep on the toilet or something.

I walk in and the walls were all painted with poop. The sink was painted with poop. The floor was painted with poop. The paper towel dispenser had poop all over the front of it.

The poor guy had gone to the bathroom, got confused and tried to remember what toilet paper was. He saw me and knew I was there to help, but he was nonverbal. His way of saying thank you was to gently take his hand and rest it under your chin.

He did so, but his hand was also still covered on poop.

I'm used to poop. It's a normal job hazard in that line of work. But something about having to clean myself and every surface in the room from caked poop while somebody else gave the poor guy a shower...that kind of story sticks with you. To this day I can't look at finger paints without feeling a little queasy.

Alt tabbed once too many times, clicked drop database, clicked yes. Realized what I'd done and panicked.

Deleted the user db for the east coast auth server for the game America's Army: Operations. Thankfully it was the secondary so we just redid replication.

My first salaried job was also my first proper IT job and I was a "junior technician" ... the only other member of IT staff was my supervisor who had been a secretary that got a 1 week sysadmin course and knew very little.

The server room was a complete rat's nest and I resolved to sort it out. It was all going very well until I tripped over the loose SCSI 3 cable between the AIX server and it's raid array. While it was in use.

It took me 2 days to restore everything from tape. My supervisor was completely useless.

A few months later I was "made redundant", leaving behind me everything working perfectly and a super tidy server room. I got calls from the company asking for help for the following 6 months, which I politely declined.

My first week on a new job I ran a DELETE query without (accidentally) selecting the WHERE clause. In Prod. I thought I was going to get fired on the spot, but my boss was a complete bro about it, and helped with data restore personally.

Everyone at that company was great both professionally and personally. It's the highlight of my 30+ year career.

I have a small PC I use for exposing a private PC to the wider web via nginx proxy. It had two accounts on it: mine, and one I called "remote" with some basic password I set up to forward the proxy connection.

One day, this machine started making 100% CPU noises, for several hours. Wtf? I check the processes and a Tor node had been setup and was transmitting gigabytes to some Russian IP.

My brain goes into panic mode, I kill the process, wipe the remote user, and eventually pull the Ethernet plug.

I wish I hadn't wiped the user directory as I wanted to know what was being sent and where. Nonetheless the logs showed that several Russian IPs had been attempting an SSH brute force for literally months and one finally guessed "remote" and weak password I set for it.

I have decades of experience on Unix system, and I cringe having made such a rookie mistake.

Lesson learned: change the default SSH port to a transient port, have one dedicated SSH user with a non-standard username, and use auth-key entry only.

I still wonder what was being sent over that Tor node, and why it required all the CPU cores. My best guess is crypto mining, or it was used for a DDOS attack net somewhere.

All those times someone accidentally printed a hundred blank pages out of the printer because they went to the very bottom of Microsoft Excel while messing around and unknowingly inserted the space bar in the bottom bar before printing.

Several years ago, when I was more just the unofficial office geek, our email was acting up. Though we had Internet access as normal. At the time, email (Exchange) was hosted on-prem on our server. Anything server related, I'd contact our MSP to handle it. Which usually meant they'd simply reboot the server. Easy enough, but I was kinda afraid and hesitant to touch the server unless the MSP explicitly asked/told me to do something.

I reported it to our MSP, expecting a quick response, but nothing. Not even acknowledgment of the issue. This was already going on for like an hour, so I decided to take matters into my own hands. I went to the server, turned on the monitor...and it was black. Well, shit. Couldn't even do a proper shutdown. So I emailed again, waited a bit, and again no response.

Well, if the server was being unresponsive, I figured a hard shutdown and reboot would be fine. I knew that's what the MSP would (ask me to) do. What difference was them telling me to do it versus just me doing it on my own? I was going to fix email! I was going to be the hero! So I did it.

Server booted up, but after getting past the BIOS and other checks...it went back to black screen again. No Windows login. That's not so terrible, since that was the status quo. Except now, people were also saying Internet all of a sudden stopped working. Oh shit.

Little did I know that the sever was acting as our DNS. So I essentially took down everything: email, Internet, even some server access (network drives, DBs). I was in a cold sweat now since we were pretty much dead in the water. I of course reached out AGAIN to the MSP, but AGAIN nothing. Wtf...

So I told my co-workers and bosses, expecting to get in some trouble for making things worse. Surprisingly, no one cared. A couple people decided to go home and work. Some people took super long lunches or chitchatted. Our receptionist was playing games on her computer. Our CEO had his feet up on his desk and was scrolling Facebook on his phone. Another C-suite decided to call it an early day.

Eventually, at basically the end of the day, the MSP reached out. They sent some remote commands to the server and it all started working again. Apparently, they were dealing with an actual catastrophe elsewhere: one of their clients' offices had burned down so they were focused on BCDR over there all day.

So yeah, I took down our server for half a day. And no one cared, except me.

My better ones are too legally dubious to post, but I do have one about fairly mundane office drama.

A coworker once dropped some particularly angry comments about a manager in the work chat instead of our private one. I panic post some inane shit to try and hide it before hurriedly tabbing over to the private chat to tell her to delete it. Too late. Along with a very clearly 'upset but trying to be professional' reply, there are some ominous words spoken about how this proves the existence of our private chat and action will be taken if this is the kind of thing being said in it. But it's clock out time for our manager and on a Friday so it gets shelved until Monday with no action taken.

Our private chat wasn't exactly secure so there was fair chance our bosses would access to it. I spend the rest of my work hours that day scrubbing it of the most damaging things I had said while trying to leave enough unflattering stuff that it looked somewhat natural. It wasn't particularly spicy all told, it was mostly just "how to do x?" without sounding incompetent in front of people who dictate whether you get paid or not, but better safe than sorry. We're still sure that our coworker who dropped the bomb is going to get shit canned though.

Monday comes around and we're all waiting for the hammer to come down. Each moment that goes by we expect the retribution is going to be worse. Around midday I realize we've got a different manager than usual overseeing us, but the usual is still clocked in. I spot a bunch of higher ups have away messages saying they're in a meeting and have been for hours. Then in our work chat comes a "x is typing" from one of them, who very rarely says anything there. I message one of my coworkers putting my bet that this was it and to brace for punishment.

The typing message from this person goes on for a good 20 minutes. It's going to be a big one.

The message finally comes. Our coworker was fired.

...and so was everyone else except myself and one other person. They were getting laid off. The meeting I noticed wasn't about our punishment, it was an emergency meeting because an important contract hadn't gone through. Company got gutted.

I worked at a pizza chain and there was a hurricane. Thankfully we only got heavy rain but I was a delivery driver and almost every other place was closed. I opened with someone and we stayed for like 10 hours straight. By the time we had to leave, we were dead tired and there would be only 2 people left working and they had dozens of orders left and they had to do delivery, cook, AND ANSWER CUSTOMERS. No, the job didn't pay enough.

I broke the home page of a big tech (FAANG) company.

I added a call to an API created by another team. I did an initial test with 2% of production traffic + 50% of employee traffic, and it worked fine. After a day or two, I rolled out to 100% of users, and it broke the home page. It was broken for around 3 minutes until the deployment oncall found the killswitch I put in the code and turned it off. They noticed the issue quicker than I did.

What I didn't realise was that only some of the methods of this class had Memcache caching. The method I was calling did not. It turns out it was running a database query on a DB with a single shard and only 4 replicas, that wasn't designed for production traffic. As soon as my code rolled out to 100% of users. the DBs immediately fell over from tens of thousands of simultaneous connections.

Always use feature flags for risky work! It would have been broken for a lot longer if I didn't add one and they had to re-deploy the site. The site was continuously pushed all day, but building and deploying could take 45+ mins.

no work related but am overfill sink with water changer because forgot to remove drain cover

is flood

am get in trouble also ._.

I once pushed a git commit with youtube link as the commit message. Nothing terrible, some completely random video. Still, it looked really weird in the commit history. Turns out you can edit this if you have access to the server and I did have access to the server.

One time in the same company I found a random youtube link in the middle of a java class. Yes, it was still compiling. No I didn't commit it.