That title sounds impressive until you realize it just means I’m the guy who keeps $14 billion in client assets from vanishing into the digital void while executives take credit for my oxygen. Donald had risen through the ranks by taking credit for other people’s work and playing golf with the board. Chloe, his niece, had been hired as a “digital transformation architect,” which is like calling yourself a brain surgeon because you watched a video about headaches. “Effective immediately,” Donald announced on a Friday, “we’re moving to a modernized system.
Chloe will be leading the initiative. ”
I asked what he meant by “modernized. ”
He said my protocols were outdated, that clients wanted innovation. I told him those protocols were the only thing standing between this company and a $200 million class action lawsuit.
One wrong command and you don’t just lose data, you lose people’s life savings. He laughed and said he’d take innovation over stagnation any day. The board applauded. Monday arrived, and I walked into a different world.
Chloe had been given full administrator access overnight. When I opened my laptop, everything looked fine until I checked the logs. I said, in the kind of calm that comes right before a Category 5 hurricane, “What did you do to the encryption protocols? ”
She smiled.
“We made them faster. Removed some legacy steps. ”
She had stripped the encryption layers. It was like removing the vault door from a bank because it took too long to open.
I grabbed the phone and called Lawrence Montgomery, our general counsel, but the lines produced nothing but static. Voice communication is the first to go when the system starts eating itself. Then came the sound of footsteps on the stairs. Someone was sprinting down 14 floors because the elevator system was starved of processing power.
Maria from compliance burst through the lobby doors, gasping, “Is Gerald still here? Please tell me he is here. ”
She told me the database was corrupted. Account balances showing zero.
Client records degrading by the minute. I told her that with encryption disabled, the first bot would detect the vulnerability within 15 minutes. 40,000 people, including retirees and teachers, would have their identities stolen. Then Chloe said, “If we’re down when Asian markets open, we lose $800,000 per hour.
”
I asked her if she knew what she had done. She said she was just following Donald’s orders. Just then, the revolving door spun and Lawrence Montgomery walked in. He asked what was happening.
Chloe tried to explain we were modernizing. I said, “There is a difference between prophecy and 16 years of reading system logs. ”
Lawrence asked what I meant. I told him I was the only person who read the documentation, because when you’re guarding $14 billion, being boring is a safety feature.
We stepped into the elevator and entered chaos. Screens flickering. Alarms echoing. Donald was there, yelling at anyone who would listen.
Lawrence demanded a full status report. I said, “Client records start degrading after 6 hours without checksums. We’re already past that. ”
Donald tried to shift blame, saying his team was fixing things.
I told him to understand that regulatory compliance is not a choice. Under Sarbanes-Oxley Act section 7262, he had to certify these internal controls. If he couldn’t, and if he covered it up, he faced personal liability under 18 U. S.
C. Donald went pale. Lawrence looked at me. “You knew this was coming?
”
I said, “I read the documentation. That includes every line of Chloe’s code. ”
He asked what I wanted. I told him I wanted the authority to fix the system, and a written agreement that no technology decisions are made without my approval.
Donald said I was overreacting. I replied, “Then start preparing your audit defense. Because there’s a federal auditor outside the building, and he’s going to want to know why 40,000 client records were exposed. ”
Lawrence grabbed his desk phone, which ran on copper lines and still worked.
He restored all credentials for user account Gerald Vance. Then he looked at Donald and said, “Pack your things and leave the building immediately. You’re done. ”
Donald yelled that this was Lawrence’s niece playing with systems she doesn’t understand because he gave her access.
Lawrence said that was on him, and if they didn’t leave, he would involve the board. I looked at Chloe. She was crying in the break room, mascara streaked down her face. I told her to pack her things and leave.
I told her if she touched another keyboard in this city, I would personally ensure the regulators knew exactly what she did. Then I grabbed my notebook and walked into the operation center. I killed all external network connections immediately. We went dark for exactly 4 minutes.
Maria asked what I was doing. I said, “Don’t try to parse the data yet, just dump it. Chloe forced the database into a processing loop. ”
I told everyone to unplug everything.
We had to let the system die to save it. I sat in the darkness, sipping my cold coffee, waiting for the system to settle. A single line of green text appeared: “System recovery initiated. Integrity check in progress.
”
Green text began to fill the screens, restoring compliance tables. The latency was actually lower than before. Lawrence walked in, looked at the screens, and said nothing. He stood there for a long time, realizing that my rigidity was the only thing that had saved his entire legacy from collapsing into nothingness.
The federal auditors arrived exactly 30 hours later. They examined everything. They noted that our system was one of the most secure they had reviewed all year. We passed section 7262 without a single citation or negative finding.
It was a complete triumph. Turning what should have been a corporate execution into a master class in security engineering. I walked out of that room with a massive salary, corporate equity that would pay for Emily’s education twice, and absolute control over the company’s technology. We moved my team to the top floor, away from executives who didn’t understand their work.
When young engineers ask me for advice, I tell them to read the documentation. I tell them to protect their work and never let a manager tell them they are too rigid, because when the storm hits, it is the rigid structures that stand while the flexible ones wash away. I look at my screens, all glowing green. The system is running perfectly.
I whisper, pouring a drop of whiskey into my mug, “To the documentation. ”
The system was safe, and so was my team. It was a new era, one built on engineering excellence and absolute integrity.
And I was going to make sure it stayed that way for a very long time.
