My voice is usually a low, flat rasp—twenty years in server rooms and a pack-a-day habit I kicked but still miss every time a man interrupts me. I was mid-sentence during the all-hands engineering sync, explaining the new architecture, when Derek cut me off. “If you break the transaction reconciliation module, you don’t just break things—you lose client money,” I said, staring straight into the camera lens. They all knew my code, the spine, was the only thing keeping this Frankenstein platform standing.
“As I was saying, the new architecture will be entirely serverless,” Derek said, not even looking at me. So, before I tell you how I systematically dismantled his life and career with the precision of a laser cutter, do me a favor. I didn’t text the CEO or HR. I opened my notes app and started a new file titled “The Funeral.
”
The output was empty. Two days later, the reorg email went out. The irony was thick enough to choke on. “What’s this?
” I asked, keeping my face blank. Derek explained he needed someone to dig into the legacy code and document every single function before deprecation. He was turning me into a librarian—the architect of the entire system, the woman who stayed up seventy-two hours straight during the series B crash, rewriting database sharding logic into instruction manuals for the idiots replacing me. “So, no more active development?
” I said. “No more commit access to the production environment,” Derek said, looking relieved. I was a wolf domesticated against its will. But I had a secret buried in a thick folder, pushed under birth certificates and tax returns.
The startup pays a yearly fee for the right to use the core system. In the event of unauthorized modification by non-certified personnel without written consent from Iron Back Systems, the licensee forfeits rights to the software effective immediately upon notice. Derek had assigned a team of outsourced contractors—non-certified personnel—to rewrite my code. I logged into the Iron Back admin portal, a server humming quietly in a Virginia data center, monitoring the heartbeat of the whole startup ecosystem.
The next two weeks were a masterclass in entropy. The contractors worked in a time zone where no one was ever awake at the same time. Their GitHub commits looked like they were written by an AI fed on Red Bull and regret. They hard-coded API keys directly into the source code.
I noticed everything. I said nothing. “You need to tell him,” my colleague Marcus said. “Not this time,” I replied.
The first crack appeared on a Thursday—a small latency spike. Then came their “optimization update. ” They called it “no downtime deployment. ” It was a suicide note written in Python.
In layman’s terms, if two people tried to move money at the same time, the system would lose track of which came first. It would double-debit, double-credit, or just set the money on fire. I could have invoked clause seven right then. I could have been the hero.
But if I stopped him now, Derek would spin it into a win. No—the crash had to be his. The ashes had to have his fingerprints all over them. Seven minutes after I flagged the risks, Derek replied all: “Native handling.
Weekend deployment. Low traffic. ”
If I was going to watch the world burn, I wasn’t going to do it on an empty stomach. For the first time in ten years, if the server crashed, my phone wouldn’t scream.
I ordered pizza. I waited. The server started making that noise—the kind you ignore if you’re incompetent. I stayed offline, watching the alert ticker through the side door.
Debits were duplicating. Credits were vanishing. Records were dissolving. Marcus messaged: “Sam, the logs say license expired.
We can’t access the source code. ”
I finally logged into Slack. The general channel was a screaming match. The CEO was frantic.
I uploaded the PDF of the 2011 contract—the one Derek never bothered to read. Then I went offline. I waited two full minutes in the digital lobby before letting them into the encrypted room. The CEO, Robert, looked pale.
Derek looked like a man watching his own funeral. “You violated the terms of service of the core infrastructure,” I said. Derek stammered, started to blame the contractors. Robert looked at me.
“What do you want? ”
“Both,” I said. “Severance and a ten percent consulting fee. ”
“If I wire this, is it fixed?
” Robert asked. “If you wire it,” I said, “I invoke clause seven, terminate the license, then I roll back Derek’s update, then I restore the database from the backup I personally made on Friday night because I knew this clown would crash the car. ”
It was the first time I’d smiled all day. I pasted the wire instructions into the chat.
The only sound was airport announcements in Derek’s background. “You should probably get on that plane, Derek,” I said. “It’s a long walk home. ”
Incoming wire transfer: $2,450,000.
00. The private key was sixty-four characters long. Then I ran the rollback script. The terminal flew, lines of code scrolling faster than the eye could read.
Finally, the output stopped. “System status: online,” I said. “Check the dashboard. ”
Robert stared.
“He’s resigning effective immediately. ”
At one o’clock, the all-hands email went out: “Leadership changes and system stability. ” The engineers knew the truth. Marcus sent me one last text: “You’re a legend.
”
I typed my resignation effective immediately and walked into my living room. The company still pays my licensing fee on the first of every month. No questions asked. Derek?
I looked him up the other day—he’s selling used cars. I still code, but I code for me. And every now and then, I get a ping on my encrypted server. The load balancer calls home.
It’s still there. They forgot the first rule of engineering: hardware eventually fails. So, to all the Dereks out there, driving your leased BMWs to jobs you’re unqualified for—be careful who you mute.
