The Last Commit

The calendar notification arrived at 9:47 a.m.

“Quick sync – 10:00 a.m.”

Satoshi stared at it for three seconds longer than necessary. The meeting had no agenda. No shared doc. Just two names: Satoshi and Maya from People Operations.

In twelve years of working at the company, Satoshi had never had a “quick sync” with Maya.

The coffee in the mug next to the keyboard had gone cold. Outside the window, Tokyo was bright and sharp—winter sun cutting through cold air, the kind of January morning where everything felt precise.

Satoshi closed the code editor. Seventeen open tabs. A support request halfway reviewed. A Slack thread with the team about the new model pipeline.

All of it suddenly felt like someone else’s work.

At 9:58, Satoshi stood, stretched, and walked to the small conference room on the third floor. The one with the frosted glass door and the table that always wobbled slightly on one side.

Maya was already there. So was Tanaka-san, Satoshi’s manager. Tanaka’s face had that careful, practiced neutrality that people wear when they’re about to deliver bad news they didn’t choose.

“Thanks for coming,” Maya said, gesturing to a chair.

Satoshi sat.

The conversation lasted eleven minutes.

It was professional. It was kind, in the way that efficient processes can be kind. There was language about “organizational realignment” and “strategic prioritization” and “difficult decisions.”

Maya slid a folder across the table. Severance details. Benefits continuation. Outplacement services.

Tanaka said something about Satoshi’s contributions being valued. About how hard this was. About staying in touch.

Satoshi nodded at the right moments. Asked two clarifying questions. Signed the form.

And then it was over.

Walking back to the desk felt longer than it should have. The hallway was the same. The fluorescent lights hummed the same hum. But the building had already started to feel like a place Satoshi used to work.

At the desk, Satoshi opened the laptop one more time.

There was the support request. Still waiting. Still half-reviewed.

Satoshi typed a short comment: “Looks good. Approved. Good luck with the deployment.”

Then Satoshi closed the laptop.

There wasn’t much to pack. Twelve years, and it fit in a backpack. A notebook. A coffee mug with a faded conference logo. A small potted succulent that had survived three desk moves.

The phone buzzed.

A Slack message from Wei, a teammate two desks over: “Hey, you okay? Saw Tanaka-san walking you to that meeting.”

Satoshi typed: “Yeah. Just got laid off. I’m good. Talk soon.”

Three dots appeared, then disappeared, then appeared again.

Finally: “I’m so sorry. Can I call you later?”

“Yeah. Later’s good.”

Satoshi slung the backpack over one shoulder and walked toward the elevator.

On the way out, Satoshi passed the wall where the company’s mission statement was printed in large, sans-serif letters:

“Building systems that scale human potential.”

Satoshi stopped.

Looked at it. He noticed he was holding his breath. A long sigh slowly escaped .

Then kept walking.

Outside, the air was cold and clean. Satoshi walked for a while without direction. Hands in pockets. Breath visible in small clouds.

There was a small park two blocks away, one of those pocket parks tucked between office towers. Satoshi sat on a bench near a bare ginkgo tree and pulled out the notebook.

For twelve years, Satoshi had worked on systems that learned, optimized, and scaled. Good systems. Useful systems. Systems that helped people write faster, code faster, decide faster.

And now one of those systems—or something like it—had probably flagged Satoshi’s role as redundant.

Not in a cruel way. Just in an efficient way.

Engineer, mid-level. Twelve years tenure. Salary: above market rate for output. Conclusion: optimize.

Satoshi wrote one sentence in the notebook:

I helped build the systems that just optimized me out.

It wasn’t bitter. It was just… true.

Satoshi sat with that for a while.

The park was quiet. A woman walked past with a small dog in a sweater. A deliveryman hurried by, phone pressed to his ear. Life moving forward, indifferent to one person’s sudden irrelevance.

After a while, Satoshi’s phone buzzed again.

This time it was a text from an old colleague, Jun, who’d left the company two years ago to teach high school computer science.

“Heard the news. I’m sorry. You doing okay?”

Satoshi typed back: “Yeah. Weird, but okay.”

Three dots.

“If you want to grab coffee this week, I’m around. No advice. Just coffee.”

Satoshi smiled—small, real.

“I’d like that.”

Another buzz. This time, an email. Subject line: “Your Outplacement Services – Next Steps.”

Satoshi didn’t open it.

Instead, Satoshi opened a note on the phone and started typing.

Not a résumé. Not a plan. Just… thoughts.

What made me useful wasn’t just the code. It was the part where I asked: “Should we build this?” It was the part where I slowed down. It was the part that noticed people.

The systems don’t have that part. They can’t.

So what now?

Satoshi stared at the question.

No answer came.

Not yet.

But sitting there, on a cold bench near a bare ginkgo tree, Satoshi felt something unexpected:

Not relief. Not fear.

Just… space.

Space to ask what “useful” meant when it wasn’t tied to a job title. Space to wonder what came next without rushing toward the answer. Space to be a person, not a productivity unit.

The company had optimized Satoshi out.

But Satoshi wasn’t done.

That was the part they couldn’t measure.

Satoshi stood, zipped the backpack, and started walking again.

This time, toward home.

Tomorrow, maybe there’d be a plan. Maybe there’d be fear. Maybe there’d be applications and interviews and all the machinery of finding the next thing.

But today?

Today, Satoshi would sit with the question.

And that was enough.

If your job title disappeared tomorrow, what would still make you useful?

Is it your skills? Possibly the part of you that notices people? Or that you ask, “Should we?” Maybe that you slow down when everyone else is sprinting?

Write down what makes you useful. One sentence.

That’s the part no system can optimize out.

Your turn: What’s your answer?

If this story might help someone you know, would you forward it to them—or share it with a friend who could use it this week?