The server room hummed its usual lullaby, a steady drone that had become the soundtrack of my nights. At 26, I’d never written a line of code before I took this job, but I’d learned the system’s heartbeat better than anyone. It was my ship, my responsibility, my quiet domain. Then Avery walked in with her linked-in smile and her buzzwords that sounded like they were generated by a chatbot having a seizure.
She was 24, had never touched a terminal, and spoke only in “synergy” and “vibes. ” She’d been hired to “modernize” the platform, and she had a plan. “We need to make the submission process fun,” she announced at the Monday meeting, her eyes scanning the room for approval. “Students are stressed.
We want good vibes only. ”
I pointed out the obvious, that the system was built for stability, not spectacle, that every extra feature added load to the servers. She smiled at me with that pitying look people reserve for the outdated. “That’s why we’re bringing in developers from her agency,” she said, gesturing to a woman I’d never seen before.
“They understand the aesthetic requirements. ”
Three weeks before the semester’s final exams, they deployed the confetti. A burst of digital rain that exploded across the screen every time a student submitted an assignment, accompanied by a tinny dance track. It was exactly what they asked for.
It was also a time bomb. I saw the code on deployment day, the kind of sloppy script that made my teeth ache. It wasn’t malicious, just incompetent. Every confetti burst wrote to the database, and if 10,000 students hit submit at once, the database lock would timeout, and the whole system would crash.
I flagged it. I wrote a report. I explained the math as simply as I could. Avery’s response was a long, dramatic exhalation of air that signaled I was being difficult.
“You just don’t get it,” she said. “The kids love it. Engagement is up. ”
“Then the engagement will eat your database,” I said.
She laughed. “That’s why we have you. ”
I could have fixed it. I could have reverted the change, tightened the locks, put a simple cap on the API calls.
It would have taken me ten minutes. But that night, sitting in the glow of my monitors, I thought about every time they’d ignored my warnings. Every time they’d asked for a miracle with a deadline of yesterday. Every time Avery had taken credit for the system I kept alive.
So instead of fixing it, I opened a new ticket in my private backlog, encrypted it under a folder labeled “doomsday,” and wrote a single comment: *Good vibes only. *
The kill switch was the easy part. There was a script buried in the system’s core, designed for catastrophic data breaches or server fires, allowing a super admin to instantly freeze all active exams to preserve data integrity. It had never been used.
I cloned it, renamed it “vibe check protocol,” and modified the trigger conditions. I wrapped it in layers of obscure variable names that Kinsley, their new developer, couldn’t decipher even if she knew where to look. If the system was running dangerous code, it would check if a certain admin account was still active. If the account wasn’t active, if I wasn’t there to stop it, the protocol would execute.
It wasn’t malicious. It was a perfectly logical response to a system running unapproved code. If they had simply reverted the confetti, if they had done the one thing a competent team would do, the kill switch would deactivate. They just had to fix their own mistake.
They never did. The day before the exams, Avery called me into her office. She had that look, the one she used when she was about to deliver news she considered a kindness. “We’re restructuring,” she said, her smile faltering for a microsecond before reassembling itself into a mask of pity.
“Your position is being eliminated. We hope you understand. ”
I understood. I understood perfectly.
The system was now their responsibility, and I had just made sure they would be held accountable for it. I thought about the 250,000 students who were about to log in. The single mothers taking night classes. The kids on scholarship who couldn’t afford to retake a class if the system ate their final paper.
I looked at Avery and said, “Ever write a rollback script? ”
She blinked. “Excuse me? ”
“It’s what you use when you realize you’ve made a terrible mistake,” I said.
“You should learn it. ”
I left the building with my box of belongings, a cactus I’d named Earl, and the encrypted drive tucked into my bag. The crossing was almost complete. I got into my car.
I resisted the urge to check the public URL. That was the rule. If I checked, I was involved. If I was involved, I was liable.
I drove home, poured a drink, and waited. The first call came at 7:45 AM the next morning. Priority low, it was just a user complaining that the site was “acting a little quirky. ” I let it ring.
The system was doing exactly what it was designed to do, failing the people who failed it. At 9:42 AM, the first pebble slid down the mountain. The error logs started filling with authentication failures, the server had begun to eat its own memory, and every time a student tried to log in, the confetti exploded, then the browser froze. The second call came at 10:00 AM.
I picked up my coffee and walked inside. I watched the metrics from my home terminal, the beautiful, cascading chaos of a system dying from within. By noon, the phone was ringing off the hook. The panic in Avery’s voice when she left a message was better than any reality TV show I had ever seen.
“Tessa, please just tell us the password,” she begged, her voice cracking. “The system locked us out. We can’t get in. Please, we’re begging you.
”
I didn’t call back. My phone rang again and again. I screened every call. On the second day, the exam results were lost, corrupted by the recursive lockout loop.
On the third day, the news reports started. 250,000 exams gone permanently. Students sobbing in dorms. Universities threatening lawsuits.
The CEO’s press conference where he promised an investigation. I waited until the panic had reached its peak, until they had exhausted every option and every excuse. Then, on the fourth day, I drove into the office. The security guard recognized me and let me in.
I walked past the empty desks, past the silent phones, and into the server room. The red alarm lights were pulsing, the fans spinning at full speed. The system was in a coma. I sat down at the console.
I opened a terminal. I navigated to the vibe check protocol. Kinsley had tried to fix it, but she’d only made it worse, locking herself out in a recursive loop. She would never guess.
The code was mine, written in a way that only I could unravel. The system took a deep breath. The patient stabilized immediately. Response time, 45 ms.
No data loss. The exams were intact, just frozen. I ran the rollback script, and the confetti code was swept away, replaced with the clean, boring reliability of the old system. No more pink error messages.
No more affirmations. I drove home and slept for twelve hours. The next morning, my phone rang once. It was Sterling, the CEO.
“Do whatever you have to do,” he said, his voice hollow. “We’re stepping back. The engineers are in charge now. We’ll put out a statement.
”
“No marketing,” I said. “I’ll write it. I’ll email you the text. ”
I typed it out while they waited: a simple, honest message to the students.
*We are reverting to the reliable system. We are stepping back to let the engineers do their jobs. * I replaced the error message with something cleaner. *System status: stable.
*
On Wednesday, I drove back to the office. The parking lot was full. I walked in, and Greg, the junior dev, stood up. Then another dev.
Then the whole engineering team. They all started clapping. Greg laughed, and pointed to the corner of my old desk. My cactus was still there.
Earl must have watered it. Sterling came out of his office, looking ten years older. “60,000 concurrent users at peak,” he said, his voice shaking. “No feature deprecated.
No data lost. We’re all healed. ”
I took Earl home with me that day. He was healthy, thriving despite my absence.
I thought about the rollback, the clean code, the students who got their grades on time. I thought about Avery, who still hadn’t learned what a rollback script was. Resolution: no feature deprecated. The system is stable.
And I’m still the one who keeps it breathing.
