I Let the Server Die on Purpose
I have spent twelve years working in the IT trenches, and if there is one thing I have learned, it is that people can be incredibly cruel to the staff keeping the lights on. For three miserable years, I worked at a high-pressure marketing firm where the management culture was toxic, and the higher-ups viewed the IT team as little more than glorified servants. We were invisible until something broke, and then we were public enemies number one. Among all the people there, a manager named Kevin was the undisputed king of being awful. He was the kind of person who seemed to get a genuine thrill out of making other people feel small. He would call my desk repeatedly throughout the day, his voice tight with fake urgency, to scream about trivial things like his printer being out of paper or his mouse feeling a little sluggish. He never gave me time to speak; he would just vent his frustrations and slam the phone down before I could even explain a solution. It was degrading, and honestly, it made my life a nightmare. What hurt the most was that he made it his mission to ruin my reputation. He would fire off aggressive emails to the directors, painting me as incompetent or lazy, just to deflect from his own lack of planning. I spent those three years feeling constantly anxious, waiting for the other shoe to drop, wondering if that day would be my last. It was an afternoon, the kind where the office energy is buzzing because everyone is ready to head out for the weekend. The company was hours away from a massive, high-stakes project launch that everyone had been working on for months. I was in the server room, which was usually my only sanctuary, when Kevin burst in. He was fuming. Apparently, his calendar wasn't syncing, and he had decided that was the biggest crisis of the century. He walked right up to me, his face turning an alarming shade of purple, and he physically poked my chest with his finger. He leaned in close and told me that if I did not fix his calendar in exactly five minutes, he was going to make sure I was out of a job by that day. The way he looked at me, with such pure, cold contempt, did something to me. He slammed the door so hard as he left that the entire room shook, and the metal racks rattled. I sat there in the silence, staring at the humming servers, and something inside me just snapped. I had spent months documenting the building’s infrastructure, and I knew for a fact that the cooling system was held together by little more than hope and duct tape. I had written a small, quiet script months ago, mostly as a 'what if' experiment, that could remotely override the thermal monitoring and shut off the cooling fans. I had never intended to use it, but standing there after Kevin’s display, the temptation was overwhelming. I didn't fix his calendar. Instead, I sat at my terminal, my heart thumping against my ribs, and I executed that script. I watched the logs scroll by on my screen with a detached sense of calm. Within four minutes, the temperature in the server room spiked violently. The ambient noise changed from a steady hum to a frantic, high-pitched mechanical scream. Then, the alarms began to blare. The emergency cooling fans died instantly, and the system did exactly what I knew it would: it protected itself by pulling the plug. The office lost power in a blink. The lights cut out, the humming stopped, and suddenly the entire building went dead. Our website vanished, the internal network died, and the big project launch was officially incinerated. Kevin came back moments later, his face almost unrecognizable with rage, but he was completely baffled. He couldn't understand how everything could go dark at that exact second. I acted completely shocked. I put on my best 'concerned IT guy' face, looking at the blinking, dead hardware with feigned horror. I told him that the heat must have triggered a catastrophic failure in the main power unit and that the hardware was cooked. He was so busy trying to figure out how to explain the failure to the angry clients calling his cell phone that he didn't even stop to interrogate me. It cost the company a small fortune in lost time and recovery efforts. I spent the next twenty-four hours pretending to work frantically to 'fix' a mess I had created myself. I played the hero, pulling an all-nighter, bringing things back online slowly enough that everyone believed I was working miracles. The directors even ended up giving me a nice bonus for my dedication to staying late and saving the day. Kevin stopped bothering me after that; he was too busy trying to save his own career and dealing with the fallout of the clients who were ready to drop us. He never once suspected that the supposed incompetence he loved to complain about was actually a calculated masterstroke. I still have that script hidden away on a secure drive, tucked far out of sight. I rarely open it, but sometimes, when I’m at my new job and some entitled person pushes me a little too far, I pull it up. I don't run it, of course, but I look at the lines of code and remember that I have the power to bring the world to a halt if I really want to. It’s a dark comfort, but it helps me get through the day.