The first time I ran our transaction engine, it was on a 2014 MacBook with a cracked screen and a fan that sounded like a jet engine taking off. We didn’t even have desks, just a rented corner in a co-working space that smelled like kombucha and broken dreams. That code was mine. Not in a petty, territorial way.
I mean typed line by line, sleepless night after sleepless night, optimized down to the byte. You spend three years nursing a platform into existence, you don’t just write code. You pour pieces of your damn brain into it. Then came Derek.
He showed up at our Thursday all-hands wearing a Patagonia vest and a $1,200 smartwatch. He couldn’t stop adjusting it, like it was his pulse that powered it. “I’m here to bring structure,” he said, grinning like he just invented capitalism. Eric was the same kind of guy.
Said “blockchain” as a verb and used “agile” like it was a personality trait. Didn’t know how to run a terminal window, but boy, could he pitch. Lots of synergy, scalability, user-centric paradigms. He liked talking about low-hanging fruit while holding a smoothie.
You know the type. At first I ignored him. Startups go through phases like bad tattoos and worse cap tables. Founders get scared.
Investors push for polish. Suddenly your hacker crew turns into a hoodie-clad TED talk lineup. Fine. I kept to my corner.
I knew the back end. I was the back end. But Derek didn’t like corners. He wanted spotlights.
He started checking in with me, asking leading questions like, “Do you think we still need legacy logic now that we’re pivoting to Ooth 2? ” Like it was a quiz show and I was the one with something to prove. Then came the phrases. Resource realignment.
Leaner workflows. Moving redundancies. He was sniffing around the team structure like a wolf in Lululemon. Still, I played nice.
Laughed. Gave short answers. Focused on work. Until one Monday morning, I tried to run a staging deploy and got a red banner: access denied.
At first I thought it was a glitch. I double-checked my SSH keys. Ran the script. Nothing.
I asked Jenna in DevOps. She blinked twice and said, “Oh, weird. I thought you asked to be removed. ”
I hadn’t.
Someone had. Now look, I’m not saying I don’t enjoy a slow-burn mystery as much as the next caffeine-guzzling back-end goblin. But you ever smell a fire before you see smoke? That’s what this was.
Subtle. Sharp. Wrong. Like sour milk in your coffee.
You know the second it hits. Later that day, I noticed a weird commit on the repo. Not mine. Some junior engineer I’d onboarded last year who now apparently had full access.
His note: “Refactoring legacy modules for clarity. ”
Which modules, you ask? My modules. Ones I documented so clearly even a distracted golden retriever could follow them.
Two days after that, I walked past the whiteboard wall outside the conference room and stopped cold. The systems diagram was there. Except it had been wiped and redrawn. Same structure.
Same flow. Except where it used to say “Sophie’s encryption layer,” it now just said “Secure Ocore. ” No initials. No footnote.
Just vanished, like I’d never been there. That’s when I started logging everything. Access changes. Commit histories.
Slack deletions. HR invites. I wasn’t angry yet. Anger comes later.
This was the quiet part. The observation phase. A sinking suspicion that maybe Derek didn’t just want to optimize workflows. Maybe he wanted to erase the people who built the damn thing before the big launch.
Rewrite history before the spotlight hit. I didn’t say anything. Not yet. Because while Derek was busy setting the stage, I was checking the trapdoor.
And darling, I’d built it myself. The thing about being erased is it doesn’t happen all at once. It’s not dramatic. It’s not a scream.
It’s more like waking up and realizing your reflection’s missing from the mirror. You’re still brushing your teeth. Still wearing the same hoodie that smells like three years of code reviews and cold brew. But the glass gives you nothing back.
It started with the internal wiki. I built it from scratch. Documentation for every microservice, API behavior, encryption sub-layer, rollout order, failure recovery scripts. Most engineers treat internal docs like the junk drawer in their kitchen.
Open it only when something’s broken. But mine was color-coded, referenced, cited, like it was the constitution. So imagine my surprise when I caught a Slack notification. Derek had asked our CIS admin for a full archive of the internal documentation.
Not the live version. Not a link. A download. Full permissions, into a shared drive named, wait for it, “Migration v2.
”
No mention of me. No invite. I pinged Ben privately. “You sure that’s protocol?
”
He took two full minutes to respond. He said, “You were consulted, were you not? ”
That’s when the back of my neck got cold. Two days later, the whiteboard in the hallway was rewritten again.
This time, the encryption module wasn’t even named. Just a blue rectangle that said “Security Layer: Proprietary. ” No initials. No labels.
Just a ghost box where my life’s work used to be. But the real kicker came in the form of a slide deck. I was reviewing an internal pitch presentation, supposedly to help the marketing team better visualize the product story. Page five: team bios.
I scrolled. Derek. Jenna. Eric.
Guy from analytics I’d never even seen in person. And then there it was. Lead Developer: Connor T. Connor.
My mentee. My code baby. The same Connor who once submitted a pull request that would have hard-deleted our user base if I hadn’t caught it in staging. His smile beamed from the slide like a Labrador that just ate a USB stick.
The title slapped next to his face like a post-it on a masterpiece. Lead dev. I closed the deck. Took a breath.
Opened my password manager. And started quietly backing up everything. Local config files. Key rotations.
Endpoint logs. License validation scripts. Not to sabotage. Not yet.
Just preparing, like a surgeon laying out the instruments. The incisions weren’t coming today. But they were coming. At the next standup, Derek was all teeth and buzzwords.
“We need a new culture,” he said, voice echoing in the glass walls. “A young culture. Dynamic. Disruptive.
”
He looked at me when he said “disruptive,” like I was the stale quesadilla in his innovation brunch. I smiled. Tilted my head. “Ah, yes.
Nothing says disruption like erasing the person who built the engine. ”
He laughed like I was joking. Everyone else did, too. Of course they did.
That’s the thing about slow betrayals. No one notices until the lights go out. And by then, they’re too busy panicking to ask who cut the power. But I wasn’t panicking.
I was cataloging. Every line of code they touched. Every commit that suspiciously skipped my branch. Every Slack thread mysteriously deleted.
I even wrote a little script that pinged me whenever someone accessed files with my signature encryption markers. Just a ping. Just a whisper. And the pings were getting louder.
One night around 1:12 a. m. , I watched a remote session log from Derek’s IP hit my license validation wrapper. He didn’t even know what he was looking at.
Ran a grep for the word “owner” and closed it. No changes. Just curiosity. Or maybe paranoia.
Either way, he didn’t realize he’d tripped a silent alert. He was trying to understand the keys now, but it was too late. That part of the house didn’t have stairs. Only a chute.
And once you go down, there’s no climbing back up. So I sipped my tea, adjusted my notes, and kept smiling. Let them pretend I was gone. I hadn’t even started.
I was halfway through debugging a latency spike in the account mirroring microservice when the calendar invite hit. No subject line. Just “Join HR Conf Rm-BB. ” Ten minutes from now.
No context. No warning. The kind of thing that makes your spine straighten before your brain catches up. I clicked accept.
Didn’t pack my bag. Didn’t close my tabs. Just walked. Conference Room B had that sad startup vibe.
Used beanbags. A whiteboard that still said “Q3 Goals” from a year ago. And a broken HDMI cable dangling like a noose. Derek was already inside.
So was Dana from HR. Dana, who always overcompensated with soft smiles when they were about to shove you off a cliff. “Sophie,” Dana said, motioning to the chair like I’d won a prize. “Thanks for making time.
”
I didn’t sit. Derek cleared his throat. He had a folder open. Paper, not digital.
Must have thought it made him look more prepared. “We’ve been reviewing the team’s current structure as we prepare for launch. And after careful analysis—” he began. “You’re letting me go,” I finished.
Dana blinked. “Well, we prefer to say the role has been made redundant in light of upcoming shifts in our go-to-market strategy. ”
I stared at Derek. “You don’t even know what my role is.
”
He didn’t flinch. “Your code’s excellent. It really is. But we need someone more agile.
Someone who aligns with the new product vision. You tend to overbuild, Sophie. And honestly, you’ve become hard to work with. ”
That last line landed like a warm fart in an elevator.
“Hard to work with. ” That catch-all term for women who know what they’re doing and refuse to act impressed by men who don’t. I could have launched into a monologue. Could have detailed every subsystem Derek didn’t understand.
Asked him what “agile” even meant in the context of back-end encryption dependencies. But I didn’t. I just asked one thing. “So you’re sure the code belongs to you now?
”
Derek leaned back, his smirk calibrated to TED talk smug. “All IP created on company time is company property. ”
I smiled genuinely. First time in weeks.
Dana handed me a generic HR pamphlet. Healthcare rollover info. COBRA nonsense. Employee exit checklist.
I didn’t even look at it. Just walked out. Calm. Quiet.
Like a doctor leaving the OR after calling time of death. My laptop was still open when I got back to my desk. No one had touched it. The terminal was blinking.
The session still live. I sat down. Ran a final script. And deleted my private encryption key.
That key wasn’t stored anywhere else. No copy. No backup. Not even in my cold wallet.
It was the only bridge between their app and the license validation module buried in the back end, like a landmine in a sandbox. Without it, everything would still look functional. Until the moment it wasn’t. Then I opened one more script.
Something I’d written months ago, in a moment of dark foresight. Trigger: sentinel in init equals production. The command didn’t look like much. It just returned: “Auto-trigger protocol armed.
”
That was it. No alarms. No flashing lights. Just a quiet contract with future chaos.
Derek and his frat-tech disciples had spent weeks trying to scrub my name from the system. They never noticed that the system still asked for me. Every time it booted. Every time it compiled.
Not loud. Just a whisper. And now that whisper would become a scream. They thought they’d locked me out.
They didn’t know I’d written the damn door. And before I left, I changed the hinges. Rewired the bell. Painted a target on the welcome mat.
It wasn’t about revenge. Not exactly. It was about truth. Truth coded into logic, into dependencies, into immutable checks the system could not bypass.
They stole something. And soon, the code would let them know. I shut the laptop, left it on the desk. Didn’t even take my mouse.
Marissa picked the coffee shop. Of course she did. She had taste. Always had.
UX/UI lead, queen of intuitive flow, hated unnecessary scroll bars like some people hate war crimes. She was the reason our app felt effortless. Users didn’t need tutorials. They felt their way through, like the app was reading their mind.
Derek never understood that. Said her designs lacked “virality. ” Translation: She didn’t make the buttons big enough for him to find with his thumb. We sat outside, drinks sweating on the patio table, while some freelance podcaster in the corner recorded hot takes into a Blue Yeti.
Marissa wore sunglasses too large for her face and an expression too tired for her age. “He rewrote the design layer in Bootstrap,” she muttered, stabbing her straw through the ice. “I checked the latest commit. It looks like a WordPress theme from 2012.
”
I winced. “I heard he’s pitching it as ‘minimalist’ now,” I offered. She snorted. “Minimalist?
Or like bankrupt? You planning to burn the place down? ”
I shrugged. “Already lit the match.
”
We didn’t talk about it directly. Didn’t need to. There’s a language shared by the exiled. The ones who built things and got pushed out the moment VCs smelled an IPO.
Marissa didn’t ask what I’d done. She just raised her cup in a silent toast. Afterward, I walked home. Logged in.
My watchers were still pinging. Nothing had changed. Not really. They’d moved a few config files.
Aimed a few folders. But the bones of the system were untouched. The deployment plan still followed my original flow. They didn’t even know which files mattered.
That’s when I knew Derek and his shiny new hires had no idea what they were launching. The license validation system I’d written had a heartbeat. It called home every time the app booted. Staging.
Dev. Prod. Normally it asked for a timestamped token from my personal key, then moved on. No token, no problem in staging.
It bypassed with a dummy handshake. But prod was different. I opened the back-end module and typed for hours. Fingers gliding like a surgeon’s scalpel.
No shortcuts. No comments. Just cold logic. I built a subroutine disguised inside the license wrapper.
Something lean, tucked into a rarely touched branch of code handling version mismatches. I called it Sentinel. If the app hit production without a valid handshake from my key, Sentinel would wait three seconds. Then it would lock the database, freeze session states, and overwrite the UI with a simple message pulled from a hard-coded string: “Stolen property detected.
Self-destruct initiated. ”
It wasn’t malware. It didn’t destroy data. It didn’t steal anything.
It just stopped the show. Loudly. The best part? I wasn’t hiding it.
The code was right there, open, but buried in complexity, obscured by naming conventions that looked benign—functions that sounded like they handled analytics or compliance checks. If anyone did spot it, they’d assume it was legacy logic. Nobody touches legacy logic. Not when you’re days from launch and your whole brand image is hanging by a single KPI.
I wrote it clean. Tidy. Legally bulletproof. All within my scope of past responsibility.
No intrusion. No external access. No call-home servers. Just logic.
And logic doesn’t lie. Once I was done, I ran it in a sandbox three times. Each time it worked exactly as planned. In dev mode, it waved.
In staging, it smiled. But in prod, with no token, the countdown began. And then the database sealed itself like a vault. After the final test, I logged out and deleted every trace of my login history.
They’d never know I’d been there. The trap wasn’t malicious. It wasn’t even vengeful. It was justice.
Quiet correction for arrogance, for theft, for pretending you could cut the engine out of the car and still expect it to drive. The keys were gone. The ignition was still there. But the moment they tried to start it?
Boom. Three seconds. I slept like a baby that night. Derek’s face was suddenly everywhere.
LinkedIn carousels. Podcast thumbnails. Banner ads in subway stations. All tight fades, wrinkle filters, that tech-bro smirk he probably practiced in the mirror after brushing his teeth with imported charcoal paste.
“The future of secure transactions,” he told one podcaster, perched in a studio that looked like it had been furnished by a crypto influencer with ADHD. “We rebuilt the architecture from the ground up. Clean. Scalable.
Totally bulletproof. ”
I was sautéing onions when he said that. I laughed out loud. Burned the onions.
Didn’t even care. He said “we. ” He meant “I. ”
By the time he hit “bulletproof,” I half expected him to claim he wrote the entire back end in Morse code using a soldering iron and sheer grit.
The host nodded sagely. “That’s what real vision looks like,” he said, like Derek had just revealed fire to a cave full of idiots. The press kits followed. Slick videos with animated flows.
Fake dashboards. Graphics that didn’t match the actual UI. TechCrunch ran a feature calling it “the Stripe killer. ” Wired used the phrase “disruptive genius.
” Some lifestyle blog dubbed Derek “the Steve Jobs of fintech. ”
I’m not saying I drank after reading that. But the bottle of red in my kitchen definitely got a little lighter. And I wasn’t the only one noticing.
The investors were drooling. Series B funding landed overnight. VC firms with names like Iron Scale and Nimbus Partners started tweeting about the app. Someone put up a digital billboard in SOMA.
Just a black background, the company’s neon logo, and a countdown clock ticking toward launch day. The irony? The clock was ticking for them, too. They just didn’t know it yet.
From my little apartment, surrounded by houseplants I mostly forgot to water, I watched it all unfold like a Netflix drama I’d already spoiled for myself. The tension was gone. No anger. No jealousy.
Just detachment. Watching a fool in a horror movie walk into the dark basement with a butter knife and no flashlight. They’d taken everything. The credit.
The spotlight. The illusion of control. But they hadn’t taken the system. Not really.
The system still recognized me. Or more accurately, it refused to function without me. Like a stubborn old dog refusing food from a stranger. That’s when I wrote the email.
Simple. Anonymous. No signature. No hyperlinks.
Just a single line, sent to a personal address I’d kept from a board member who once told me, after a particularly grim code freeze, “You’re the only one here I’d trust with my bank account. ”
I typed: “Watch your app on launch day. ”
No flourish. No threat.
Just a nudge. A flick of a match in a room soaked in gasoline. Then I bought a ticket to the launch. Not a backstage pass.
Not a press credential. Just a seat in the crowd. Paid full price. Let them think I was gone.
Let Derek think his kingdom was rising. He never looked up to see the cracks in the foundation. And now I didn’t need to lift another finger. The trap was in place.
The script was loaded. The countdown had already started. And I had the best seat in the house. The night before a launch always smells like stress, burned coffee, whiteboard markers, and unwashed ambition.
I’d lived through enough of them to recognize the pattern. Frantic Slack pings at 2 a. m. Git commits named “final-final-for-real-this-time.
” Someone crying in the restroom because Jenkins failed again. But this one was different. From the outside, everything looked polished. The office windows in SOMA glowed late into the night, filled with silhouettes huddled around glowing screens.
The countdown ticked below twelve hours. Investors were flying in. Swag bags were packed. There were even branded cupcakes with the logo printed in edible ink.
But inside the repo? Chaos. My remote watchers started buzzing mid-afternoon. A junior engineer, Ravi I think, was desperately commenting and uncommenting blocks of JSON in the deployment config, trying to get something to pass validation.
He wasn’t working alone. Two more commits landed back to back, both labeled “temp fix,” and both rolled back within minutes. I could almost hear the panic from four hundred meters away. The anomaly?
The prod build was rejecting the license handshake. Cleanly. Quietly. The app would still load, just long enough for the lockout to trip and seal the vault.
I watched for a while. They still hadn’t touched the trigger sequence itself. Too buried. Too camouflaged.
I’d made it look like a dead legacy hook from an old compliance framework. Something no one wanted to touch this close to launch. That’s the thing about engineers under pressure. They only lift what’s labeled urgent.
Real dangers hide under the things they think they understand. And Derek? Oh, Derek. Apparently one of the interns flagged the issue in a Slack thread.
“This module keeps calling a null handshake loop. Should we investigate? ”
The thread died instantly. Derek replied with a single message: “Ignore it.
We don’t need her. She was slow and overcomplicated everything. ”
Slow? That was rich, coming from a man who thought Git was a productivity app.
I smiled. Not because I was angry. Not even because I felt vindicated. But because Derek was about to learn what “overcomplicated” really meant.
At 9:42 p. m. , I ran one final test in my sandbox. Triggered the prod handshake without the key.
Three. Two. One. Boom.
Lockout. Data freeze. UI override. Message flashed: “Stolen property detected.
”
The purge was clean. No rollback. No debug logs. Just a cold stop.
And the key? Still gone. Irrecoverable. Burned like a match.
I hadn’t written a back door. I didn’t need one. The trap wasn’t for me. It was for them.
I poured a glass of water, turned off my monitor, and for the first time in months, I slept. No dreams. No anxiety. Just rest.
But I wasn’t the only one up that night. At 1:17 a. m. , my watcher logged a new access attempt.
Derek. He was poking around the back end himself now, clearly trying to identify the handshake failure. Ran a grep for “validation. ” Found the module.
Opened it. Spent twenty-six minutes inside the file. Then he made one small change. A comment added to the top: “TO BE REFACTORED POST-LAUNCH.
”
He didn’t touch the logic. Didn’t even understand it. But he wanted to mark his territory. When he hit save, the system threw a warning.
He ignored it. Tried to deploy a hot fix. It failed badly. Rollback initiated.
Jenkins threw a tantrum. He deleted the thread from Slack before anyone could reply. The team never saw the alert. But I did.
From my end, everything was perfect. The play was set. The actors in place. And in just a few hours, the curtain would rise.
One performance only. The venue was some polished, overengineered tech cathedral in downtown San Francisco. A converted factory with exposed brick, ironic Edison bulbs, the kind of minimalist stage design that screams “we blew the budget on ego. ” Rows of white chairs filled with people who smelled like VC money and virtue-signaling cologne.
Everyone was overdressed and overconfident, holding artisanal lattes and limited-edition conference badges like they were golden tickets to a smarter, sleeker future. And there, at the back, near the sound booth, where no one important ever looks, sat me. Plain black dress. No name tag.
No plus one. Just a front-row seat to my own quiet apocalypse. Derek strutted out fifteen minutes late, because of course he did. He wore all-black Steve Jobs cosplay with worse posture, pacing with a wireless mic clipped to his collar and that same rehearsed smirk.
Cameras flashed. Phones filmed. The live stream counter ticked into six digits. “Good morning, innovators,” he began, voice oozing faux humility.
“Today isn’t just a product launch. It’s the beginning of a revolution in secure transactions. ”
I tilted my head. There it was.
“Secure. ” He loved that word. Tossed it around like seasoning. Even though he had no idea what it meant under the hood.
Security wasn’t a feature. It was the skeleton. The bloodstream. The thing that bleeds silently when you cut it wrong.
He clicked the clicker. A slide appeared behind him. Glowing animations. Fake user metrics.
Flashy transitions that would have made Marissa dry heave. Logos scrolled by. Partners. Early adopters.
Media mentions. Each one a lie stacked on top of a stolen blueprint. I scanned the room. VC reps in tailored suits.
Influencers live-streaming with ring lights clipped to their phones. The original founders sat off to the side, looking glassy and tired. Names still on the paper, but souls long since cashed out. Derek launched into a demo.
On the massive screen behind him, he held up a tablet. Running the app live, he claimed. Production. The crowd leaned forward.
The camera zoomed in. He tapped. I held my breath. But nothing happened.
Not yet. The app loaded. The UI glowed. The buttons worked.
For now. The system had rules. Checks. Timers.
The license validation waited for just the right moment. Just long enough for them to be sure it worked. Derek turned to the crowd. “When we started this journey,” he lied, “I knew we needed a back end that was scalable, modular, and self-healing.
We built one from scratch. ”
I didn’t even blink. He was still talking, but I’d stopped hearing words. My pulse was steady.
No anger. No adrenaline. Just quiet observation. I watched his hands.
His face. The lines at the corners of his eyes, twitching between rehearsed confidence and creeping doubt. He tapped another screen. Triggered a sample transaction.
Still nothing. The app processed the fake payment. The UI cheered. Applause broke out.
The journalists typed faster. Hashtags popped up like weeds. One influencer whispered to her phone, “It’s actually working. ”
I waited.
The lockout was never supposed to hit instantly. It waited for one thing. One real interaction. One genuine session from a verified live user in production, with no key.
That’s when the timer would begin. That’s when the mask would peel off. That’s when Derek’s smile would crack. But for now, he stood there, glowing in front of his stolen kingdom.
And I just sat there near the back, with a half-smile and a full heart. The curtain was up. The trap was awake. And the next click would decide everything.
The second he tapped the screen, something shifted. Not loud. Not obvious. Just off.
A flicker. The app didn’t respond the way it had in rehearsals. The screen stuttered. Then dimmed.
For a heartbeat, it just hung there, like the system itself was holding its breath. Then it went black. The room, once buzzing with nervous energy and marketing fumes, went dead silent. Derek blinked.
The massive display lit up with stark red font on a matte black void:
“Stolen property detected. Self-destruct initiated. ”
Then came the countdown. Three.
A ripple of confusion surged through the audience. Two. Phones came up. A woman in the front row gasped, dropped her branded water bottle.
One. And then chaos. The app froze hard. The animation stalled mid-frame.
Transaction fields evaporated. Live sessions evaporated. Then the database locked completely. A cascading sequence of terminal-level commands executed in the background.
Unseen by most, but not by the devs watching the stream on their laptops backstage. One by one, user data nodes purged their active caches. Session tokens invalidated. The UI collapsed into a system-wide lockdown interface with one final message: “Unauthorized launch protocol detected.
Source license missing. Shutdown complete. ”
In the crowd, someone whispered, “The hell is this? ”
Someone else shouted, “Was this planned?
”
Derek’s mic picked up a sharp inhale. But no words came out. His hands hovered above the tablet like it had turned into an explosive device. He tapped again.
Nothing. He swiped. Nothing. He turned to the stage crew, eyes wide.
“Cut the feed! ” he hissed. But it was too late. The live stream had already caught it.
People were screen-recording. Tweeting. Commenting. “WTF just happened?
”
“Is this part of the launch? ”
“Did they get hacked? ”
A reporter near the front stood up, phone camera fixed on Derek. “Is this a cybersecurity failure?
” she asked, live, her voice cutting through the tension like a scalpel. “Was the app compromised? ”
And then he looked up. Saw me.
Sitting near the back. Legs crossed. Arms folded. Expression calm.
Still surgical. I didn’t smirk. Didn’t flinch. Didn’t blink.
Just held his gaze. He froze. Every drop of color drained from his face. Looked like a child who just realized the stove was still hot.
A man beside him—one of the junior engineers who’d been promoted too fast—leaned in and whispered, audible enough for the mics to catch: “She did this, didn’t she? ”
Derek didn’t answer. Couldn’t. Because that was the moment he realized what I’d built was never just code.
It was a verdict. He hadn’t just stolen software. He’d stolen authorship. Integrity.
Credit. And credit doesn’t go quietly when ripped from its roots. Now, with every camera pointed at his sweating face, every VC watching in horror, every investor’s phone vibrating in their pockets with panicked texts from assistants and analysts, the system had responded. Not with a lawsuit.
Not with a hacker. With logic. Cold. Elegant.
Immutable. I stood. Not rushed. Not dramatic.
Just rose from my chair and turned toward the exit. As I passed the doors, someone in the hallway asked, “Is the launch canceled? ”
I kept walking. Let Derek answer that, if he could.
The street outside the venue smelled like burnt espresso and shame. Clusters of people stood frozen on the sidewalk, blinking at their phones, scrolling through live reactions to the onstage meltdown they just witnessed. One guy in a Tesla hoodie muttered into his AirPods, “Yeah, cancel the wire. Just pull it.
All of it. ”
A woman in stiletto boots snapped, “No, don’t think it was a stunt, Brad. The app died. ”
Behind me, the venue was bleeding executives.
VC reps bolted toward black SUVs with tinted windows and zero patience. A cameraman chased down a board member who fake-smiled, said “We remain optimistic,” before vanishing into a vehicle that peeled off like it owed someone money. My phone buzzed. Unknown number.
But I knew who it was. “Holy shit,” the message read. “They’re saying you broke it. ”
I stared at the screen for a moment.
Then typed back: “No. I protected my work. They broke the law. ”
No emoji.
No follow-up. Just the truth. Because that’s what it was. Derek didn’t fail because of sabotage.
He failed because he thought ownership came from signatures on offer letters and nice blazers with startup logos stitched into the lining. He forgot that systems have memory. And the one I built remembered everything. By evening, the launch was being dubbed “the tech implosion of Q4” on Twitter.
Some influencer posted a slow-mo of the red-screen moment with dramatic music layered over it. The hashtag #StolenPropertyDetected trended for six hours. Day two: internal leaks hit Reddit. Devs posting anonymously about the weeks of ignored warnings.
A screenshot of the license handler code even made it to Hacker News. A few people figured it out. Just enough to connect the dots. Not enough to reverse-engineer what I’d done.
Day three: the board fired Derek. Quietly, of course. With a PR statement about “leadership realignment” and “refocusing on long-term goals. ”
Day four: the app was pulled from stores.
All demo servers shut down. The homepage now read: “We’re undergoing maintenance to bring you a better experience. ”
And day five? Well, that one started with an email from a CTO at a competing firm.
Someone who’d seen the meltdown and apparently loved a good underdog power play. “We’re looking to rebuild our infrastructure from the ground up,” she wrote, privately. “On your terms. ”
I marked it unread.
I wasn’t in a rush. Instead, I walked to my favorite coffee shop. The one with the flickering Edison bulb and a barista who spells my name “Sophie” every time. Took my usual seat by the window.
I opened my laptop. The same one they hadn’t even asked me to return. Same one that still carried traces of the early builds, the midnight test logs, the first version of the encryption layer, written while half-asleep and three espressos deep. I updated my resume.
Scrolled to the bottom. Typed: “Proprietary back-end architecture. Secure. Non-transferable.
”
Then I sipped my coffee. And hit save. The revenge wasn’t fire. It wasn’t fury.
It was just the truth, written in code. A reminder that some things can’t be stolen. Only imitated, badly, by people who think appearances are structure and buzzwords are blueprints. I never heard from Derek again.
That was the real win. And that’s the story. Take care of yourselves out there.
The world’s unpredictable enough.
