My Arrogant Boss Deleted My Code and Fired Me — He Didn’t Realize It Was The Company’s Engine
Part 2
The walk from the conference room to my desk felt like crossing a border between two warring nations.
The open-plan office hummed with the usual mid-afternoon energy.
Sales guys were ringing gongs and the espresso machine was screaming.
None of them knew that the company was already dead.
They were walking around on a corpse that hadn’t started to smell yet.
I grabbed a cardboard box from the supply closet.
It was a happy onboarding box meant for new hires.
I packed my personalized keycaps, my noise-canceling headphones, and a framed photo of my cat, Pixel.
“Brenda.”
I turned to see Gary, the lead systems administrator.
He was a pale man who looked like he lived in a server rack.
“Is it true?” Gary whispered, looking toward the glass-walled conference room.
Tyler was still gesticulating wildly at the whiteboard.
“Did he actually delete the optimization module?”
“He clicked delete and then confirmed it,” I said.
Gary’s face lost what little color it had.
“But the load balancers rely on that module.
If it is gone, the health checks will fail in about nine minutes.
Then the auto-scaler will try to spin up new instances to compensate.
Since the base image pulls from the main branch, the new instances will spin up broken.
It’s going to be an infinite crash loop.”
“Yep,” I said.
“I have to stop the deploy,” Gary said, reaching for his phone.
“Don’t,” I said.
My voice was sharp, cutting through his panic.
“He fired me explicitly for obstruction.
If you intervene now, you’re undermining the CTO.
He’ll fire you too, and you have a mortgage and twins on the way.”
Gary swallowed hard.
He looked at the server status dashboard on the big screen.
All the lights were green.
It was the calm before the red storm.
“So, we just let it burn?”
“It’s already burning, Gary.
We are just waiting for the smoke detectors to notice.
Let him see what lean looks like.”
Gary nodded slowly.
“I didn’t see you.
I was in the bathroom.”
“Good man,” I said.
I walked toward the elevator.
My phone buzzed with a notification from our internal chat.
Brian was messaging me.
Tyler was trying to run the build manually, it was throwing errors, and he was yelling at the compiler.
I didn’t reply.
I just deleted the app from my phone.
As the elevator doors closed, I saw Tyler storming out of the conference room.
Our eyes met through the narrowing gap of the steel doors.
I just watched him realize that he was completely alone with a disaster he had created.
I walked out of the building and hailed a ride to the acquiring company’s headquarters.
I was no longer just a fired employee.
I was the competition.
And I was on my way to sell the blueprint in my head.
Would Tyler realize his catastrophic mistake before the multi-million dollar acquisition meeting tomorrow?
Part 3
Tyler would never realize his catastrophic mistake before the multi-million dollar acquisition meeting tomorrow.
He was too blinded by his own arrogance to see the trap he had sprung on himself.
The conference room had smelled like stale, burnt coffee and nervous sweat, a specific olfactory blend that usually preceded a disaster in the Seattle tech scene.
Brenda had sat at the head of the mahogany table, her hands resting flat on the cool surface of her laptop.
She wasn’t nervous.
Nervousness is a reaction to uncertainty, and Brenda was never uncertain about her code.
She was the lead back-end engineer at Streamline, a startup that had spent the last five years trying to disrupt the logistics supply chain.
For five years, she was the one who made sure the disruption actually happened instead of just timing out.
Standing at the whiteboard had been Tyler, the founder’s son.
Tyler was a twenty-seven-year-old with a shiny MBA, a smile that looked like it was purchased from a catalog, and a brand new title.
Chief Technology Officer.
He had held the position for exactly four days.
In those four days, he had managed to use the words synergy, paradigm, and blockchain in a single sentence, which Brenda was pretty sure was a felony in at least three jurisdictions.
He had pointed a laser pointer at her projection, the red dot wavering on the screen, dancing over the architecture diagram of the optimization module she had spent the last six months building.
He called it spaghetti.
He called it bloat.
They knew the module wasn’t bloat.
It was a masterpiece of load balancing logic, the reason their platform could handle ten thousand concurrent requests without melting the servers into silicon slag.
It was the engine.
Calling it cluttered was like an amateur critiquing a finely tuned race car engine without understanding the mechanics.
Brenda had kept her voice steady, adjusting her glasses, explaining it was the latency reduction protocol that improved throughput by twenty percent.
She explained that removing it would cause the response time to jump from fifty milliseconds to three seconds.
Tyler had laughed a wet, condescending sound.
Orion Technologies was looking for lean code.
He had walked over to the developer console mirrored on the big screen, his fingers hovering over the keyboard.
Brenda’s stomach had tightened.
Tyler had admin access.
She had told the founder, Craig, that giving Tyler admin access was like giving a toddler a loaded handgun.
Craig had just patted her shoulder and said his son needed to feel empowered.
Tyler announced they didn’t need complex back-end voodoo, demanding a clean main branch.
Brenda had warned him not to touch the repository.
He sneered, claiming he was cleaning house, and highlighted the core logic directory.
Brenda stood up, warning him that deleting it would collapse the staging environment since auto-deploy to production was enabled for the demo tomorrow.
With a theatrical flourish that belonged in a bad Broadway play, Tyler hit delete, then commit, then push.
The screen flickered.
The terminal window scrolled green text for a second, then stopped.
He dusted his hands off, declaring it leaner already.
The silence that followed was absolute, a vacuum.
Brian, a lead junior developer Brenda had trained from scratch, looked like he was about to vomit.
He looked at Brenda with wide eyes, pleading for her to fix it.
But Brenda couldn’t fix it.
She had felt a strange calm wash over her, the calm of a demolition expert watching the charges go off exactly as planned.
She told Tyler he had just deleted the logic layer.
The application was now a front-end shell.
It was a zombie.
Tyler turned red, accusing her of negativity and toxicity.
The room gasped.
Brian stood up to protest, but Tyler barked at him to sit down or be next.
Brenda had looked at Tyler, then at the screen where her code used to be, and then at her terrified team.
Her phone had buzzed on the table.
It had been buzzing for weeks from a blocked number.
She had ignored it out of loyalty to Craig, to the code, and to her team.
But she picked it up now.
Tyler was still rambling about fresh perspectives and rockstar ninjas, thinking he had won.
He watched her, waiting for the tears and the begging.
Brenda swiped right and answered.
It was Dan, the Vice President of Engineering at Orion Technologies, the very company supposed to buy Streamline for hundreds of millions next week.
Dan mentioned they hadn’t heard back regarding the offer.
He stated they were finalizing due diligence tomorrow, and looking at the architecture documents, Brenda was the only reason they were still interested.
The rest of the code looked like a mess.
Brenda looked at Tyler’s smirking face.
She spoke clearly into the phone, accepting Orion’s offer.
Tyler’s smirk faltered as he demanded to know who she was talking to.
Brenda ignored him, telling Dan she could start immediately because her schedule had just cleared up.
A momentary silence hung on the line as Dan checked if she was in any trouble.
Brenda locked eyes with Tyler, stating everything was perfect and she would see him in an hour.
She hung up, closed her laptop, and unplugged her charger.
The winding sound of the cord retracting was the only noise in the room.
She wished Tyler good luck with the deploy and walked out of the room.
Her heels clicked on the polished concrete floor, leaving behind five years of her life and a system bleeding out into the digital void.
Tyler shouted something about insubordination and a security escort, but she barely heard him.
She was already doing the math in her head.
Her module handled the authentication tokens.
The impending cache expiration would soon revoke administrative access for the entire staff, sealing Tyler out of his own system.
He hadn’t just fired her.
He had locked himself inside a burning building and thrown away the key.
The open-plan office of Streamline hummed with the usual mid-afternoon energy.
Sales guys were ringing gongs, marketing was arguing about font kerning, and the espresso machine in the break room was screaming.
The oblivious employees were unaware that their workplace had just suffered a fatal blow.
The startup was effectively a lifeless shell, though the decay wasn’t visible yet.
Brenda reached her standing desk, set up with three vertical monitors and a mechanical keyboard.
She grabbed a cardboard onboarding box and packed her personalized keycaps, noise-canceling headphones, and a framed photo of her cat, Pixel.
Gary, the lead systems administrator, approached her.
He whispered, asking if Tyler had actually deleted the optimization module.
Brenda confirmed it, noting he had used the graphical interface and thought he was leaning out the code.
He realized the API gateway and load balancers relied on that module.
He calculated the health checks would fail in nine minutes.
The auto-scaler would try to spin up new instances, but since they pulled from the broken main branch, they would spin up broken.
It would be an infinite crash loop.
Amazon Web Services would bill them for thousands of instances spinning up and dying every second.
Brenda agreed, popping a stress ball into her box.
Gary reached for his phone to stop the deploy, but Brenda sharply told him not to.
She reminded him she was fired for obstruction.
Intervening now would undermine the CTO, and Tyler would fire Gary too.
Gary had a mortgage and twins on the way.
Gary looked at the server status dashboard showing all green lights.
He asked if they should just let it burn.
Brenda told him it was already burning, and they were just waiting for the smoke detectors to notice.
She asked him to let Tyler see what lean looked like.
Gary nodded slowly, claiming he was in the bathroom and hadn’t seen her.
Brenda walked toward the elevator.
The message revealed Tyler’s desperate attempts to force a manual build while screaming at the resulting terminal errors.
Brenda just deleted the app from her phone.
As the elevator doors closed, she saw Tyler storming out of the conference room, looking confused.
He was holding his laptop like a shield, looking for someone to blame.
Their eyes met through the narrowing gap of the steel doors.
The whoosh of the descending car was peaceful.
Brenda walked out into the gray Seattle drizzle.
She hailed a ride to Orion Technologies.
Her phone buzzed with an email saying her workspace account was suspended.
Tyler was quick with the admin panel when panicked, but he was too late.
She was the competition now, on her way to sell the blueprint in her head.
Orion Technologies didn’t have an open-plan office.
The lobby was a cathedral of glass and steel.
Brenda walked to the reception desk and asked for Dan.
Dan was waiting, wearing dark denim and a black cashmere sweater.
He looked like a man who wrote code in the morning and negotiated acquisitions in the afternoon.
They sat overlooking Lake Union.
Dan cut the corporate dance.
He explained they had been trying to buy Streamline for six months.
But every time their engineers dug into the back-end, it was pristine.
Dan knew it was Brenda.
Brenda confirmed it was her and her team.
Dan mentioned she had said she was free.
Brenda explained that Tyler had decided to clean up the codebase an hour ago and deleted the logic module in production.
Dan’s eyebrows shot up.
Brenda clarified Tyler deleted the optimization layer that made the platform work, and fired her for trying to stop him.
He realized acquiring Streamline tomorrow meant buying a shell.
Brenda corrected him, saying it would be a front-end interface pointing to errors.
The data was there, but the engine to access it was gone.
Tyler didn’t like documentation, calling it bloat.
Dan smiled genuinely.
He admitted they didn’t want Streamline for their brand or app.
They wanted the underlying engine to power their new financial technology vertical.
Dan pulled out a tablet showing Project Vessel.
It was a high-frequency trading platform.
Since Streamline’s tech was imploding, Dan proposed building it from scratch with the architect who designed it.
He offered Brenda the position of Head of Architecture for Project Vessel.
She would be an equity partner, make three times her previous salary, choose her own team, and have full autonomy.
No founder’s sons.
Brenda looked at the schematic.
No legacy debt, no quick fixes for sales demos.
A clean slate.
She asked what happened to the Streamline deal.
Dan explained a clause in the letter of intent allowed them to walk away if the technology was significantly degraded.
Brenda thought of the red error logs flooding her former team’s monitors.
She smiled coldly and said the technology was non-existent.
Dan agreed they would walk away and build Vessel.
Brenda had one condition.
She wanted to hire Brian, Gary, and Megan once the dust settled.
Dan agreed instantly.
They shook hands.
Her phone vibrated in her pocket.
She ignored it, knowing the crash loop had started.
The infinite billing was racking up.
The fires were burning, and for the first time in five years, she didn’t have to grab a fire extinguisher.
No one screamed.
No one threw buzzwords around like confetti.
There were stand-up meetings, but they actually lasted fifteen minutes.
Code reviews were brutal but focused on the code, not the ego.
Brenda sat in her new office with a door, migrating her mental blueprints into Orion’s secure repositories.
They were building Vessel on a modern stack, something she had begged Streamline to transition to for years.
Here, resource requests were approved in five minutes.
She hadn’t blocked Brian or Gary because she needed to know they were okay.
And honestly, a small dark part of her needed to know how bad it was.
Tyler was screaming that the cloud provider was scamming them.
He had tried to edit the configuration file in a basic text editor and corrupted the encoding.
By Wednesday morning, Gary messaged that he hadn’t slept in forty hours.
Every time they patched the routing table, the front end threw errors.
Tyler kept asking why they couldn’t just undo the server state.
Gary thought Tyler was crying in his office.
Brenda sat in her ergonomic chair, sipping loose leaf tea.
She read these messages with a detachment that surprised her.
She texted Gary a potential fix but told him to go home and let it crash.
Gary replied he couldn’t because the demo with Orion was on Friday.
If they didn’t have it running, Craig was going to have a stroke.
Brenda walked out to the Orion coffee bar and saw Dan.
Dan asked how the build was going.
Brenda reported the API skeleton was up and latency was incredibly low.
Dan smirked and mentioned they were still scheduled for the final acquisition demo with Streamline on Friday.
Craig had called Dan to assure him the glitch earlier in the week was just a system upgrade.
Craig claimed they were now more optimized than ever.
Dan laughed, saying Craig claimed his CTO had personally overseen the rebuild.
Dan was sending the VP of Product and their lead legal counsel to verify.
He asked if Brenda wanted to join via video link to consult.
Brenda thought about seeing Tyler’s face when the system inevitably failed.
She didn’t need to see it.
It was a deterministic system.
Input garbage, output garbage.
Later that night, Brenda got a text from Megan in QA.
Megan revealed they were hard-coding the data.
They couldn’t fix the back-end logic, so for the demo, they were making the front-end display static files.
If Orion clicked on anything other than the happy path, the whole thing would throw an error.
Brenda stared at the screen.
Hard-coding the data was fraud.
She forwarded the text to Dan with a simple caption to ask them to filter by a date range from last year.
The static file only covered the current month.
Dan replied with a thumbs-up emoji.
Brenda leaned back in her chair, watching the sun set.
She felt a strange sense of peace.
She wasn’t the one holding the duct tape anymore.
Friday morning arrived with heavy gray gloom.
At Orion, it was just another Friday.
Brenda was in a code sprint with her new team.
They were building the authentication microservice in quiet, focused work.
But her second monitor had a terminal window open to a group chat with Brian, Gary, and Megan.
She had named the chat Lifeboat.
Tyler was sweating through his blazer, smelling like desperation.
Brian messaged that the demo was starting.
Tyler was driving, clicking through the dashboard, bragging about how fast it loaded.
Brenda took a bite of her bagel, knowing it was only fast because it was loading a local file.
Megan messaged that the Orion VP just asked to see the logistics throughput for the third quarter of last year.
Gary typed that Tyler froze.
Tyler tried to excuse it by saying they focused on real-time data and historicals were archived for latency purposes.
Megan wrote that the Orion guy wasn’t buying it.
This was the kill shot.
The archive was a lie to cover the fact that the API was dead.
Brian messaged that Tyler was typing into the browser console in front of them.
He was trying to change the dates on the fly.
Gary reported a massive red error box appeared on the screen.
Undefined is not a function.
Brenda chuckled.
Megan messaged that Tyler was shouting at the screen, blaming the Wi-Fi.
Brian typed that the Orion lawyer just stood up.
The lawyer stated the application wasn’t making network requests.
They were monitoring the traffic and knew it was a static page.
Brenda could feel the air leave the room from miles away.
The fraud was exposed.
It wasn’t just a bug anymore.
Gary messaged that it was over.
Craig looked like he was having a cardiac event.
Tyler was staring at the wall.
Brian noted that Craig turned to Tyler and demanded to know where Brenda’s code was.
Tyler repeated that he had leaned it out.
Brian messaged that Craig was screaming.
Brenda closed the chat window.
The acquisition was dead.
The massive deal had evaporated in forty-five minutes because a nepotism hire thought he could outsmart software engineering fundamentals.
Dan walked into her office an hour later.
He confirmed it was a total fabrication.
They had tried to spoof the data.
Dan stated they issued a formal withdrawal of the letter of intent.
Their legal team was drafting a notice regarding breach of good faith.
Brenda asked about the intellectual property.
Dan called it worthless without her logic layer.
It was just bad code and a nice interface.
They weren’t buying it.
They were building Vessel.
Dan smiled and mentioned Craig had asked about Brenda as they were leaving.
Craig had claimed there was a misunderstanding regarding her employment.
Dan assured her they protected their assets, and she was the most valuable asset they had.
Brenda turned back to her screen.
The Vessel code was compiling.
There were no errors and no warnings, just clean, efficient execution.
Usually, when a deal falls through, there is a press release spinning the failure.
There was nothing.
At Orion, Project Vessel was hitting every milestone.
Brenda’s team was a machine.
She was working hard, but she wasn’t exhausted.
One rainy Saturday, Brenda was reading at a coffee shop when she saw Brian.
Her former junior developer looked ten years older, with dark circles under his eyes.
He was frantically typing on a laptop.
Brenda approached him, and he jumped.
His shoulders slumped when he saw her.
Investors were pulling out after finding out about the fake front end during the demo.
Tyler was gone, effectively fired by Craig immediately after the demo.
But the damage was done.
They couldn’t restore the old code because Tyler had canceled the backup subscription to save money two weeks before he fired Brenda.
Brian’s voice cracked as he explained they had nothing.
They were trying to reverse-engineer her logic from compiled binaries, which was impossible.
Brenda softly agreed, knowing the obfuscation protocols she installed would make that take years.
Brian described patching things with duct tape and acting as a human API, running SQL queries manually for clients.
Brenda felt a pang of sympathy for Brian.
He was a good kid who didn’t deserve this.
She told him she couldn’t go back because the bridge wasn’t just burned, it was nuked.
Instead, she slid a business card across the table.
It was for Orion’s human resources department.
She told him they were hiring for the Vessel team and needed a front-end lead.
Brenda corrected him, saying Orion hated Streamline, but loved competent engineers held hostage by idiots.
She added that the same offer extended to Gary and Megan.
She told him to get out and stop bailing water on a sinking ship.
Brian pocketed the card, thanking her profusely.
Brenda joked not to use Tyler as a reference.
She walked home feeling lighter.
The collapse of Streamline wasn’t her fault.
It was a tragedy of arrogance.
That evening, Brenda got a news alert about Streamline.
The headline announced the CTO was ousted amidst the acquisition collapse, with investors alleging technical malpractice.
The article detailed the disastrous demo and mentioned internal sources describing a toxic culture of nepotism.
It didn’t mention Brenda by name.
She was just the former lead engineer whose departure precipitated the crisis.
She was the ghost in the machine.
And the machine was finally breaking down.
He was about to try one last desperate maneuver that would bring him right to Brenda’s doorstep.
A legal courier arrived at Orion on a Tuesday.
He delivered a thick Manila envelope.
Dan called Brenda into his office, stating they had been served.
They accused Brenda specifically of intellectual property sabotage and planting malicious code.
Craig was claiming Brenda had intentionally booby-trapped the code before she left, causing the system to fail.
He was claiming her module was a logic bomb.
Brenda tossed the document back, calling it insane.
She hadn’t planted a bomb.
She had built the load-bearing walls, and Tyler had knocked them down with a sledgehammer.
The collapse wasn’t sabotage, it was gravity.
Dan calmly agreed.
He noted their forensic audit of the version control logs would prove Tyler’s commit history was a smoking gun.
Craig was desperate and trying to freeze the development of Vessel.
He thought tying them up in court would force a settlement.
They were going to invite them over for a deposition.
Craig didn’t know Brenda was the head of Vessel.
He thought she was just a disgruntled employee they picked up for cheap.
The next morning, the Orion conference room was set up like a tribunal.
On one side were Orion’s legal sharks.
On the other was Craig and a tired-looking lawyer.
Brenda watched from the adjacent room via a one-way mirror.
He pounded the table, shouting that Brenda had destroyed his company.
He claimed the system worked perfectly for five years until she left.
Orion’s lawyer smoothly pointed out their records indicated Tyler initiated a deletion of the directory.
Craig sputtered, claiming Tyler was optimizing and cleaning up Brenda’s mess.
He yelled that Brenda had left undocumented dependencies and made herself indispensable on purpose, calling it extortion.
The lawyer calmly replied that it wasn’t extortion, it was engineering.
Dan signaled Brenda it was time.
The silence was instant.
Craig stopped mid-shout, his eyes locking onto her.
She wasn’t wearing her old hoodie and jeans.
She was wearing a tailored blazer.
She looked like money and power.
She greeted Craig calmly, taking a seat next to Dan.
Craig pointed a shaking finger at her, accusing her of ruining his company.
Brenda’s voice was ice cold as she stated she had built his company for five years.
She had kept it running while he spent funding on office furniture and his son’s salary.
She reminded him she had warned him about giving Tyler admin access and documented every risk, which he signed off on.
She slid a folder across the table containing the logs.
It showed every keystroke and commit.
Tyler hadn’t just deleted the module.
He had tried to replace it with code copied from a stale internet thread, incompatible with their libraries.
He didn’t just break the car, he poured sugar in the gas tank.
Dan announced they were counter-suing for defamation and frivolous litigation.
Unless, Dan paused smiling, Craig dropped the lawsuit immediately.
Craig had to admit publicly that the failure was due to internal mismanagement.
Craig looked at his lawyer, who shook his head indicating it was over.
Craig slumped in his chair, looking small.
The bluster and denial were gone.
All that was left was the math, and the math didn’t work.
Brenda told him that next time he fired an architect, he should make sure he knew where the load-bearing walls were.
Three months later, Project Vessel went live.
It wasn’t a noisy launch.
There was no confetti or buzzword-filled press release.
Just a switch flipped at two in the morning.
Brenda stood in the Orion command center, surrounded by her team.
Gary watched the server load.
Brian announced traffic was spiking.
They had just onboarded Streamline’s biggest former client, who defected after Streamline filed for bankruptcy.
Gary reported latency was a stable twelve milliseconds, and the load balancers were barely breaking a sweat.
Brenda watched the data flow on the main screen.
It was beautiful.
Streams of gold light moved across a dark map of the world, each a transaction or confirmation.
It was the system she had always wanted to build.
It was clean.
Brenda let out a breath she felt like she’d been holding for five years.
She praised her team and suggested ordering pizza.
The celebration was low-key with pizza and craft beer.
The vibe was different here.
There was no fear because they knew the system worked.
Dan walked in holding a bottle of champagne.
They were auctioning off the intellectual property and legacy code for pennies.
Nobody wanted the tainted code.
Dan laughed, calling the whole thing worthless and a cautionary tale.
Brenda asked about Craig and Tyler.
Dan noted Tyler was pursuing other opportunities, trying to pivot into fields where he didn’t need to know how things worked.
Craig was forced into retirement, losing his house and boat as investors sued him.
It was a grim fate, but Brenda couldn’t find it in herself to be sad.
Brenda asked Brian how the import script was coming.
Brian confirmed it was done and could migrate any remaining Streamline customers to Vessel in under an hour.
Brenda told him to turn it on.
They weren’t just winning.
They were absorbing.
As the sun came up over Seattle, Brenda realized she wasn’t angry anymore.
The rage and cold fury were gone.
Tyler had viewed her professional profile.
She smiled, choosing not to view his back or block him.
She let it sit there, letting him see her success and what he had deleted.
She told Gary to run a stress test to see if they could handle double the load.
The work continued.
The world kept turning.
The final act of the Streamline tragedy didn’t happen in a courtroom.
Six months post-collapse, the liquidation firm reached out to Orion for help.
They were trying to extract historical data for a tax audit, but couldn’t access the archives.
The backups Tyler hadn’t deleted were encrypted.
The private key lived in a secure vault requiring two-factor authentication.
One factor was the CTO’s authorization, which was revoked.
The other was the lead engineer’s authorization.
Brenda’s authorization.
Dan told her she had no legal obligation to help them.
Brenda knew that, but there were customer records inside.
Innocent businesses needed their tax documents, and it wasn’t their fault Tyler was incompetent.
She decided to go there one last time.
She drove to the old office.
The building looked the same, but the logo was gone.
The silence was heavy.
He thanked her for coming, noting Tyler had claimed he didn’t know the password.
Brenda walked to her old empty desk.
She pulled out her laptop and connected to the local server running on emergency power.
It still worked.
Tyler had never figured out how to change the root credentials.
The encrypted volume appeared.
Brenda pulled a USB drive from her pocket containing her private key.
Access was granted.
Kevin sighed in relief, calling her a lifesaver.
Brenda stood up, calling herself the janitor cleaning up the mess one last time.
She looked around the empty office, seeing the ghosts of her past.
She saw the ghost of Tyler deleting her work and Craig nodding along.
She wasn’t safe because she worked hard.
She was safe because she was smart.
It was Craig.
His voice was raspy and broken.
He realized too late that her module wasn’t bloat.
Brenda stopped at the glass door.
She confirmed it wasn’t bloat.
Craig whispered that it was the foundation.
She agreed, stating she had let him break it.
Brenda listened to the static on the line.
She thought about rubbing it in, but she didn’t need to.
The empty office, the bankruptcy, and the silence were loud enough.
She said goodbye and hung up.
She walked out into the rain.
Vessel had just hit massive transaction volumes, and they needed her approval for a cluster expansion.
Also, they had ordered Thai food.
Brenda smiled and got into her new car, bought with her Orion signing bonus.
She looked back at the empty building one last time.
She thought about how easy it is to destroy something you don’t understand, and how hard it is to build it back up.
Next time you delete something, make sure you know what it does.
Because sometimes, you’re not just deleting code, you’re deleting your future.
Brenda merged onto the highway, heading back to Orion, back to the builders, and back to work.
THE END
Tell us what you think about this story, and share it with your friends. It might inspire them and brighten their day.
If you enjoyed this story, read this one: My Sister-In-Law Glued My Daughter’s Hair For Views — So I Took Everything
Disclaimer
This story is a work of fiction inspired by real events. Names, characters, and details have been altered. Any resemblance is coincidental. The author and publisher disclaim accuracy, liability, and responsibility for interpretations or reliance. If you would like to share your story, please send it to [email protected].
