Chương 6
People are blaming the tools.
I typed a response.
Then deleted it.
I typed another.
Deleted that too.
Rachel watched.
“You don’t have to answer immediately.”
“I know.”
“You are allowed to be angry.”
“I know.”
“You are also allowed to not save them today.”
I looked at her.
That sentence stayed with me.
Because she knew something I had spent years avoiding.
I did not only like fixing problems.
I liked being the person who could fix problems.
There was a difference.
That evening, I opened the old laptop from storage.
I expected it to feel like evidence.
Instead, it felt like a time capsule.
The machine was slow.
The battery barely held a charge.
The fan made a strange clicking sound whenever it started.
I remembered buying it after leaving another job where my manager had taken credit for my work.
I had promised myself I would never again build something important without knowing exactly who owned it.
Then Westbridge happened.
And slowly, I stopped protecting myself.
I opened old folders.
Some contained code.
Some contained notes.
Some contained things that had nothing to do with work.
A grocery list.
A photo from a company picnic.
A reminder to call my mother.
Small pieces of a person who existed before the crisis.
Near midnight, I found something unexpected.
A folder created six years earlier.
The name was simple.
Continuity.
Inside were files I did not remember creating.
Most were technical notes.
But one document caught my attention.
Risk Assessment.
I opened it.
My own name was at the top.
I did not remember writing it.
Then I saw the date.
Five years earlier.
The document described the possibility that Westbridge had become too dependent on individual engineers rather than documented systems.
It listed recommendations.
Training.
Knowledge transfer.
Ownership reviews.
Succession planning.
I kept scrolling.
Near the bottom was a comment.
Not from me.
From the former CTO.
“Lily understands the technical risk better than anyone, but she underestimates her own strategic value.”
I stopped reading.
Not because the sentence was dramatic.
Because it was uncomfortable.
I had always thought of myself as the person behind the curtain.
The person who made things work.
Not someone who had influence.
Not someone whose absence could change the direction of a company.
The next morning, Rachel called with news.
“Westbridge held an emergency board meeting.”
“How bad?”
“Depends who you ask.”
“That sounds like a lawyer answer.”
“It is.”
I waited.
She continued.
“Some board members want to negotiate immediately.”
“And others?”
“Some want to challenge ownership.”
I closed my eyes.
“Of course.”
“There’s more.”
“What?”
“Elliot Voss resigned this morning.”
I sat up.
“He resigned?”
“Yes.”
“Why?”
“Officially?”
“Unofficially.”
Rachel hesitated.
“He claims he was not aware of the full licensing situation.”
“And do you believe him?”
“I believe he did not expect the consequences.”
“That is not the same answer.”
“No.”
She was quiet.
“Lily, there is another problem.”
I waited.
“Elliot was the person who pushed for your termination.”
I already knew that.
But hearing it confirmed changed something.
“Why?”
Rachel sighed.
“We are still trying to determine that.”
The question followed me all day.
Not because Elliot wanted me gone.
People wanted people gone all the time.
The question was why he believed removing me would help him.
At three in the afternoon, Evan called.
I almost did not answer.
Then I did.
“Hey.”
His voice sounded nervous.
“Lily.”
“What happened?”
“Can I ask you something?”
“Sure.”
A pause.
“Did you know about the ownership agreements?”
I looked at the wall.
“Yes.”
“Did everyone else?”
“No.”
Another pause.
“That explains a lot.”
“What does that mean?”
Evan exhaled.
“There was a meeting last month.”
“With who?”
“Marcus and Elliot.”
“What about?”
“Engineering structure.”
I waited.
Evan lowered his voice.
“They were talking about replacing the old systems.”
My stomach tightened.
“Replacing?”
“Yes.”
“With what?”
“I don’t know.”
That answer bothered me.
Because I knew what it usually meant.
A replacement project before understanding the existing system.
A decision made because something looked old rather than because it was failing.
“Evan.”
“Yeah?”
“Why are you telling me this?”
He was silent for several seconds.
Then he said something that reminded me how young he still was.
“Because I think I should have said something sooner.”
I sat there holding the phone.
“About what?”
“About the way they talked about you.”
The room became very quiet.
“What did they say?”
Evan swallowed.
“They said Westbridge needed to stop depending on one person.”
I almost laughed.
Not because it was funny.
Because it was almost true.
Then he added,
“But they said it like you were the problem.”
I looked at the old laptop on my desk.
The machine that had carried years of my work.
Years of solutions.
Years of mistakes.
For the first time since being fired, I stopped thinking about proving Marcus wrong.
I started thinking about what kind of company Westbridge would become if nobody forced it to confront the truth.
And I realized the answer depended on whether they wanted a repair.
Or whether they only wanted someone to blame.
And I realized the answer depended on whether they wanted a repair.
Or whether they only wanted someone to blame.
I spent the next morning doing something I had avoided for years.
I opened every message, every document, and every old project note connected to the systems Westbridge was using.
Not because I wanted ammunition.
Because I needed to understand what I had actually built.
There was a difference between knowing something worked and knowing why it had become impossible for others to replace.
I had always been focused on the next problem.
The next outage.
The next person who needed help.
I rarely looked backward.
Engineers are often praised for moving forward quickly.
Nobody praises the person who stops and asks whether the road underneath them was ever designed properly.
By noon, I had a folder full of contradictions.
May you like
Some were small.
Some were impossible to ignore.
