Chapter 3

On the third day, the explosion I had been waiting for finally hit.

At 10:00 AM, the front desk switchboard lit up like a Christmas tree.

Moments later, a client success manager ran onto our floor clutching a ringing headset, her face completely pale.

"Engineering! The client's entire user auth system just crashed! Millions of users can't log in! Their phones are ringing off the hook!"

The news hit the open floor like a detonated grenade.

Julian was the first to burst out of his corner office, staring in pure disbelief.

"That's impossible! We only pushed a small test branch to production yesterday! How could it touch their core database?!"

The client manager was on the verge of tears.

"I don't know! Their VP called screaming saying it happened right after your deployment! Our support lines are literally exploding!"

I sat back, completely unbothered.

It was the data integration module.

In my handover doc, I had flagged that exact dependency in bold red text, specifying that it could only be tested in a dedicated sandbox environment with the client’s lead engineers on standby.

Julian, obsessed with rushing out a fast win, had ordered the juniors to push code directly to the live production database.

He was an idiot trying to defuse a bomb, cutting the one wire he didn't recognize—the detonator.

The whole engineering wing collapsed into pandemonium.

Julian was screaming commands at the top of his lungs, flailing wildly.

"Check the logs! Find the bug now!"

"Roll back! Roll everything back to yesterday's build immediately!"

His orders were pure chaos.

The junior engineers, already terrified, started fumbling.

Someone checked the wrong server logs. Someone else triggered a rollback on the wrong git branch.

Panic spread through the room like wildfire.

I leaned back in my chair, watching the circus unfold in cold silence.

My phone began buzzing frantically on the desk. It was my direct contacts from the client side.

Instead of yelling, they were desperately asking what the hell happened to our team.

I typed out a polite, standard reply: I am no longer the lead on this project. Please direct all technical emergencies to the current Project Director, Julian Vance.

Then, I flipped my phone face down on silent mode.

Julian scrambled for thirty painful minutes. He didn't fix a damn thing; he only made it worse.

Error alerts kept multiplying across the dashboard, bleeding into their secondary payment systems.

Sweat drenched his collar. He couldn't keep up the act anymore.

His eyes darted frantically across the chaotic room, finally locking onto me.

There was a flicker of desperate pleading in his eyes.

I saw it. And I ignored it.

I looked down, pretending to format an irrelevant PDF.

You made your bed, golden boy. Lie in it.

At noon, the real storm arrived.

Marcus, the VP of Technology, marched onto our floor with a pitch-black face, trailing three departmental directors behind him.

"Julian! Somebody explain to me right now what the hell is going on!"

Marcus’s roar silenced the entire floor.

Julian went ghost-white. His lips trembled, unable to string a coherent sentence together.

"Marcus... we're... we're diagnosing the root cause right now..."

"Diagnosing?! It's been two hours since ten o'clock!"

"Do you have any idea how much revenue the client is losing every minute? If this account churns, don't even think about quarterly bonuses for anyone!"

Marcus was practically spitting fire.

Right then, Julian pulled a move so filthy it disgusted me.

He whipped around, pointed a shaking finger straight at the junior devs behind him, and shrieked in a cracked voice:

"It was them! The junior team messed up the deployment pipeline!"

"I explicitly walked them through safety protocols, but they cut corners to save time! That's what caused this outage!"

"Especially the crew Evelyn handed over to me—their technical fundamentals are garbage, and they have zero sense of accountability!"

In a fraction of a second, he threw every single terrified kid under the bus.

Their eyes went wide in pure horror.

Maya burst into tears on the spot.

Dead, suffocating silence gripped the room.

I watched Marcus and the directors narrow their eyes. The look they gave Julian shifted from anger to sharp, cold suspicion.

That single flicker of doubt was a scalpel, severing Julian's last shred of credibility.

The lingering weight in my chest vanished. I actually felt a wave of relief.

The second those words left his mouth, this disaster was cleanly, completely detached from me.

He had burned his own bridge to ash.

I didn't yell. I didn't stand up to argue.

There was no need to.

I quietly opened Julian Vance - Incident Log and typed out today's note:

April 17th. Day 3. Julian Vance bypassed protocol and forced an untested push to the production database, crashing the client's user system.

Following the crash, Mr. Vance immediately scapegoated the junior developers, labeling them as 'lacking fundamentals and accountability.'

I saved the document, locked it with an AES-256 password, and emailed it to my personal drive.

Then, I opened a blank document.

Right in the center of the clean white page, I typed two words:

Resignation Notice.