The terminal

Mid-January 2026. He opened a terminal.

That sentence is nothing to most people and it is most of his twenties to him. The last time he sat in front of one he was failing the semester that ended computer science for him and started the long detour. Every year afterward confirmed the verdict. He was the ideas guy. Somebody else typed.

This time the machine was on his side of the desk.

The first two weeks were brutal in the specific way that only happens when you are bad at something in front of yourself. He describes it as feeling like the dumbest man alive. Not discouraged. Not challenged. Dumb.

Then it caught.

What he found on the other side of those two weeks is the most useful thing in this entry for anybody who thinks they are too late. Pattern recognition does not care what you point it at.

He had spent twenty years pointing his at charts. At ad accounts. At funnels, split tests, conversion rates, and the far harder pattern of what a person actually means when they say what they say. All of that is one faculty. Code is a system with rules, feedback and consequences, which describes every other thing he had ever been good at.

The muscle did not have to be built. It had to be repointed.

And then there is the part that had nothing to do with code.

The noise in his head went lights-out. Cold turkey, overnight, the moment the purpose arrived. It had gone quiet in November; January is when it became permanent, because the voices had nowhere left to stand once something showed up and took the whole room.

Ten years he had tried to out-discipline them. What finally did it was having a thing to point the entire apparatus at, every day, hard enough to require all of him.

Ten years of progress arriving at once. An overnight decade — which is what it looks like from outside, and from inside is just twenty years of preparation finally finding somewhere to land.