I knew the company was heading for Digital Cliff the moment Gavin walked in wearing a vest that cost more than my first car and smelling like sandalwood and unearned confidence. And frankly, it keeps me motivated to type this out instead of throwing my laptop into the Hudson River. “Susan,” he said during our first one-on-one, leaning back in a chair that was ergonomically designed for people who actually do work. “We aren’t Facebook.
We’re a fintech startup with a disruptive edge. If we break things, we get sued into the stone age. ”
I felt a cold knot form in my stomach. His name was probably Tyler or Skyler or something that rhymes with failure.
For 8 years, I had been a mandatory attendee for the architecture review board. I knew every line of code in that system, every vulnerability, every shortcut that had been taken to keep the lights on. I messaged the project manager, a nervous woman named Janet, who survived by blending into the beige wallpaper. Ellipsis pulsing for an agonizingly long time.
“He said it’s for ideation leads only,” came the reply. That was the new label. He didn’t name me. Before, I would join the other leads.
Now, sitting with me was a political liability. One afternoon, I found a bill: a monthly invoice for a cloud optimization tool that cost $40,000 a month. I’d never heard of it. The CEO of this vendor, a guy named Chadwick, who just happened to be in a lot of Gavin’s college fraternity photos on Facebook.
The system stabilized, but not because of him. A few days later, Gavin called an all-hands meeting to announce his new cloud optimization strategy, presenting charts that were just lines going up. He demanded, loud enough for the whole floor to hear, “You’re reacting to ghosts because you’re scared of the future. ”
You work in corporate America long enough, you learn the rhythm of the hit job.
I wasn’t invited naturally, but the walls in our office were glass, and sound travels through AC ducts if you know where to listen. I knew the code for this assistant. Basically, if a customer asked the bot to list all my transactions for the last 10 years, the bot would try to do it instantly. I didn’t do anything, Gavin.
I’m a professional. I didn’t kill the bot. Instead, I throttled its bandwidth to 1%. The red dashboard turned yellow, then green.
I found the specific queries that crashed the system. And then I found something else. A single line of code, documented as “hotfix 2024-11-03,” that pointed to a private server. I was curious, so I traced it.
The server was a digital graveyard of old accounts, all owned by Gavin. And there, buried in the logs, was a script that had been running daily since the Monday he walked in. It was scraping the database for any reference to “Susan,” “legacy,” “integrity issues,” “unauthorized hardware. ” Every email I sent to the compliance officer was flagged.
Every encrypted file that mentioned the vendor invoice was marked. But the worst part: he was deleting my access tokens, one by one, and reassigning them to a kid named Mike who had been here three weeks. Mike had never touched a production system. He didn’t know what a regex was.
He thought a checksum was something you did at the grocery store. If he approved a change on a Friday afternoon, the entire cluster could go down over the weekend, and the blame would land on me, because the ticket history would show the incident originated from my workstation, using credentials I’d supposedly reset. It was a complete frame-up. Email trails, admin logs, even a memo from HR in my name complaining about being passed over for a promotion I never applied for.
I couldn’t just tell them. They’d think I was paranoid, or worse, that I was the one doing something wrong. So I built a trap. A tiny dormant line of code that triggered would swap Gavin’s fake charts with my truth dashboard.
It was a list of impossible goals designed to be failed. If I signed it, I asked, would I be the one liable when the market went south? They didn’t realize they had just handed the arsonist a box of matches. Based on the consultant’s code quality, I estimated the system had about 6 days before a catastrophic, unrecoverable data corruption event.
I had to keep the patient alive just long enough to die on stage. Wednesday morning, 2 days before the big board meeting, I tried to log into the primary oversight console. He had violated the terms of the PIP before the ink was even dry. “Jason, if the buffers are off, any write error becomes permanent across all clusters.
”
“I don’t have the permission level. Only the senior lead does. ”
“Did you tell them? ”
“Then do nothing.
Do not touch the code. ”
For the first time in 8 years, I couldn’t save the system. The system was beginning to dissociate. Then the phone rang.
A direct line from a board member. They never called staff. “I cannot verify any data rendering issues,” I said. Silence on the line.
The line went dead. I still had the master key for the AV setup. Exactly. He should have been terrified.
The night before the all-hands meeting, I didn’t sleep. This was a corporate coup d’état staged with code. It was elegant in its simplicity. Gavin’s presentation ran on a web-based slide deck platform.
He was looking down at his notes. I looked harmless, just taking notes. My name was circled in red. “Today, I am announcing a restructuring, effective immediately.
”
Instead, the screen turned a stark terminal black. A kid named Mike, who I had once helped fix a corrupted hard drive, looked at the screen, then looked at me. “I’m not attacking the company, Gavin,” I said, my voice carrying clearly. “If it breaks, we blame Susan.
” Love cashed out the stock options by then. The red text turned yellow. Then slowly, line by line, it started turning green. “System integrity restoring.
”
Two large security guards stepped out of the shadows. They froze, then slumped into chairs like deflated balloons. The all-hands is over. “Oh, enough,” so only I could hear.
I wasn’t sure I wanted the title. Turns out that cloud optimization company was funneling money into a crypto wallet they all shared. “You know, Susan, most people would have just quit. Why did you stay?
”
“It’s my code. Uptime system uptime 24H12M04s. ”
And for the first time in a long time, it wasn’t the silence of fear. It was the silence of a machine running exactly the way it was supposed to.
Life has its storms, but it also has its calm waters. See you in the next one.
