Series: AI, Ego & Regret — Bonus Chapter
Editor's Note: While compiling the old series for the book, I found this draft in the archives. It didn't fit the original lineup, but the story was too good to leave buried on a hard drive. I polished it up and decided to release it as a bonus chapter for the series. This is a work of fiction.
Act I · Dead Weight
It took me six years to turn NovaTech's AI diagnostic platform from a Python script on a single server into a production system processing four million diagnostic requests a day. Every sensor pushed data upstream. The model didn't fire on every reading, but during peak hours it handled over a hundred per second. Our clients included three Fortune 500 manufacturing giants — the biggest of which was Merit Manufacturing — plus a medical device brand you've definitely used.
Six years ago when I joined, the company had eighteen people and the CTO still wrote code. CEO Ryan Whitfield pounded the table at all-hands meetings and said, "We're building something that matters."
Three years in, we moved into a Sunnyvale office with a courtyard. Ryan drank half a bottle of whiskey at the housewarming party, put his arm around me, and told an investor, "Tom's the reason this ship stays afloat."
Three years after that, the ship told me I was dead weight.
The layoff came on a Wednesday at 11 AM. All-hands video call. Ryan sat in front of his dining room chandelier — the one that cost thirty grand — and explained that the company was going through a "strategic restructuring" to "streamline operations." Slide three had my name and the entire data platform team's — all twelve of us — sitting neatly inside a gray box.
"The affected roles are being eliminated to reduce redundancy."
Redundancy. I'd led this team for six years. Years of zero-incident operations. 99.97% recall rate. Redundancy.
HR's separation package landed in my inbox. Standard severance, an NDA, a one-year non-compete. I couldn't even work at the coffee shop downstairs, let alone a competitor.
I noticed something when I signed. Buried in my non-compete was an exception clause: "Family members of executive leadership are exempt from non-disclosure obligations regarding internal restructuring communications." It was tucked into a footnote on page fourteen in type so small you'd miss it if you blinked.
I didn't think much of it. I signed.
Act II · First Blood
Two weeks later, LinkedIn filled in the blanks.
Kevin Whitfield's new profile picture showed up in my feed. Westport University polo shirt, standing in front of the engineering school sign, teeth so white they looked AI-generated. His headline: "VP of Engineering at NovaTech | Builder | Thinker | Disruptor."
I stared at that title for a solid twenty seconds. VP of Engineering. A guy who was writing course projects three months ago, holding the same title as my old boss.
His first company-wide email went out the next afternoon — sent to all the inboxes I no longer had access to. Dmitri — one of the old-timers on the team — screenshotted it and sent it to me.
"I'm excited to announce that NovaTech is entering a new chapter. Our current platform architecture, while functional, carries significant technical debt. I'll be leading a modernization initiative to bring our stack into the next generation. Expect faster iterations, leaner deployments, and a more aggressive roadmap."
Technical debt. Faster iterations. Leaner deployments. Every word landed exactly on "I have no idea what this system does."
Dmitri's caption under the screenshot: "He asked me today if the CI/CD pipeline was a new hire."
Act III · The Model Swap
Kevin's first move wasn't architectural. It was swapping the model.
"Tom's model is six years old. It's good. But good isn't the standard anymore."
That's what he said at his first tech all-hands. Dmitri relayed it to me in a flat voice — he was past the point of being surprised.
Kevin's "modernization" meant replacing the diagnostic model I'd tuned for six years — 99.97% recall with a 0.03% false positive rate in industrial fault detection — with the newest closed-source LLM on the market. He claimed the LLM's "zero-shot reasoning capabilities" would expand coverage from 340 scenarios to "infinite."
340 scenarios. Every single one went through three rounds of labeling, two rounds of cross-validation, and at least three hundred hours of production observation before we called it done. Kevin spent three days reading API docs and decided that was enough.
At the demo, he pulled up the LLM's dashboard and told the six engineers in the room: "This thing reads the logs, understands the context, and outputs the diagnosis in natural language. No more manual rule tuning. No more feature engineering. No more bottlenecks. "
When he said "no more bottlenecks," he looked at Dmitri. Dmitri was our performance engineer. Kevin probably didn't know his name, but he knew that role belonged to "the previous era."
Dmitri didn't push back in the meeting. He messaged me afterward: "He said the LLM benchmarked against our logs. I checked his test set. Textbook fault patterns. Not a single one from a real production line."
I didn't reply. Because Kevin knew too — he picked a clean test set because clean test sets give clean results.
Act IV · Cascade Failure
Counting from Kevin's first day, by day twelve the swap was done. Kevin oversaw the engineering team himself, cutting over the old inference pipeline to the LLM's API. The switch was smooth. Every endpoint returned 200. Every green light on the dashboard stayed on.
Day fourteen, Merit Manufacturing's production line reported a fault.
Nothing major — a sensor drift on a conveyor belt. The old model had handled this exact scenario over a thousand times. Diagnosis: "Sensor drift detected, recalibration window: 72 hours." Confidence score attached. Maintenance ticket generated. Total time: 170 milliseconds.
The new model read 170 pages of production logs, spent 4.3 seconds, and produced a fluent paragraph:
"The anomaly pattern suggests a potential degradation in the conveyor belt alignment mechanism, possibly due to cumulative thermal stress on the drive unit bearings. Recommend immediate full inspection of the drive train assembly."
Translation: "I have no idea what this is, but I can write something that sounds smart."
The maintenance crew stopped the line. Pulled the drive unit. Tore down the bearings. Four hours later, they found nothing. The supervisor wrote in the work order: "False alarm. No fault found."
That was the first one.
Day sixteen, the same LLM flagged a normally running compressor as "imminent bearing failure." Another teardown. Another four hours. Nothing. The supervisor changed NovaTech's diagnostic feed status to "high noise."
Day eighteen, it missed a real fault.
Sensor readings clearly showed a hydraulic seal accelerating toward failure. The old model's rule engine would have triggered a "failure probability: 87% within 7 days" alert. The LLM read the same data and wrote: "The observed fluctuation patterns are within normal operational variance. No immediate action required."
Thirty-two hours later, the seal blew. The line was down for nine hours. Each hour of downtime cost $130,000.
Dmitri sent me the numbers — screenshots from the incident report, timeline and cost breakdown included. His caption: "Your rule engine caught faults for six years. Twenty days after they swapped it, it blew up in front of a client." I didn't reply. But I read every line.
Act V · The Ultimatum
Merit Manufacturing's incident report didn't name NovaTech — Diana did them that favor. But the customer success VP forwarded an email to the internal group chat, and Dmitri screenshotted it to me. Five sentences from Diana to Ryan, CC'd to four people: her CFO, her legal VP, NovaTech's customer success VP, and a legal department inbox.
The third sentence: "We require the diagnostic model deployed prior to June to be restored within fourteen calendar days. If that is not possible, we will exercise our right under section 6.2 to terminate the agreement."
Translation: "Put Tom's model back. If you can't, we walk."
Act VI · The Call
Three days after that email, my phone buzzed at 11 PM. No area code in the caller ID, but I knew who it was.
"Tom."
"Diana."
"Everything I'm about to say, my legal team would tell me not to say it."
She paused. I heard keyboard clicks on the other end — she might have been closing windows, making room for what came next.
"Merit Manufacturing is terminating the agreement with NovaTech. Section 6.2. Fourteen-day transition period."
I didn't say anything.
"We need someone to lead the transition. Not someone from NovaTech. You know this system better than any engineer still on their payroll. Your non-compete has two holes in it. I had my lawyers check —" she paused, like she was making sure she hadn't crossed a line. "The family-member exception was posted on an anonymous forum. Same firm that drafted your contract — anyone who reads it can see what it means. And the non-compete itself has an out: client-initiated separations don't trigger it. Also —" another pause. "Kevin's reply was effectively a written refusal. We don't need to wait the full fourteen days."
I leaned against the kitchen counter. My wife was reading to our daughter in the living room, voice soft, one word at a time. I listened to those syllables, holding the phone, feeling the world go quiet for two beats.
"Tom?"
"Send me the details," I said. My voice was calmer than I expected.
Before she hung up, I asked: "Diana — did you go to NovaTech first?"
A long silence. Then: "I did, Tom. Kevin told me the LLM is 'objectively superior' and suggested I wait for his explainability report. So I'm done waiting."
She was waiting for Kevin to realize he was wrong. He never did.
Diana sent me the explainability report right after the call. Six pages of PDF. Every section tried to prove the two false alarms and the missed fault were "edge cases," "out-of-distribution inputs," "not representative of the model's true performance." There was a comparison table in the appendix showing 98.7% accuracy on his clean test set.
He told a complete lie using a dataset that never lied.
Act VII · The Exception
The NDA's hidden exception clause was dug up by a former colleague and posted on an anonymous workplace forum. The thread title: "\"NovaTech's restructuring was literally designed for nepotism.\" Over four hundred replies."
One comment stuck with me. An anonymous account claiming to be a former NovaTech employee wrote: "Ryan Whitfield once told me culture fit was the most important hiring criterion. Turns out what he meant was 'shares my last name.'"
I screenshotted it. Didn't save it. Then I closed the browser and opened the architecture docs for Merit Manufacturing's new project.
A system isn't yours just because you didn't build it — that was Kevin's mistake. A system is yours forever because you did build it — that was Tom's fate.
AI, Ego & Regret — Bonus Chapter. This is a work of fiction. Any resemblance to real events or persons is coincidental.
📖 Stratagem 2 of the 36 Stratagems series — coming soon.
P.S. English isn't my first language. I use AI to polish the writing and smooth out the rough edges. Thanks for reading. ☕ Buy me a coffee
Top comments (2)
Tom's mistake wasn't getting laid off it was building something so deep into one company DNA that leaving it felt like amputation. The real horror isn't Kevin. It's that Kevin was allowed to happen because nobody above Tom understood what he'd actually built. The 99.97% recall rate wasn't a number, it was six years of edge cases nobody else knew existed. Diana knew. Kevin never did. That last line hit hard — a system is yours forever because you built it.
"Amputation" — that's the word I kept circling and never landed on. You're right.
Six years of edge cases that nobody wrote down because nobody thought they'd need to. Diana knew the number was real because her crew had dealt with the 0.03% false positives. Kevin walked in, read an API doc for three days, and decided he'd seen enough.
Appreciate you reading it that close, Basit 👊