← Back to Blog

Builder's Patience: The Knicks Are Champions Again

The New York Knicks are NBA champions. The last time that sentence was true, it was 1973. I have spent my whole life waiting for it, and I inherited the wait from my grandfather, who spent his.

This is a personal one. The thread, if you want a professional one, is the same instinct that runs through everything I build: patience, long horizons, and the humility to know the best outcomes still surprise you. But mostly this is about a basketball team I have loved through a lot of losing.

The ball on the shelf#

My grandfather spent his days watching the championship Knicks, the ones with Walt Frazier and Willis Reed. He passed down an image of that team, and more than that he passed down the way he talked about them, the way Clyde controlled a game and the night Reed limped out of the tunnel and the building came apart. He gave me a basketball signed by Willis Reed. It has sat on a shelf my entire life as a kind of promise: this team was great once, and it could be again, and you should stick around to see it.

He waited a long time for this one. I like to think he is watching tonight, keeping score the way he taught me to.

The lean years did the teaching#

I did not get the great Knicks. I got the ones that taught patience the hard way.

I watched Latrell Sprewell and the 1999 Knicks claw out of the eight seed all the way to the Finals, then run into the Spurs and lose. Close enough to ache. After that came the years I followed the team mostly through box scores, reading about the Stephon Marbury trade and the Eddy Curry trade and convincing myself each one was the turn. They were not. I wrote during Linsanity, when Jeremy Lin made February feel like a playoff run. I remember being genuinely thrilled the night Chris Duhon broke the franchise single-game assist record, which tells you exactly how lean things were. You learn to find the joy in the scraps when the meal never comes.

That is the part that doesn't fit on a highlight reel. Most of being a Knicks fan was not winning. It was showing up anyway.

The roster I drafted in my head#

Here is the confession. For years I built this team in NBA 2K, in GM mode, over and over, constructing dynasties out of a franchise that could not construct one in real life. And in those builds, two players were always on my board: OG Anunoby and Karl-Anthony Towns. OG for the pure athleticism, and because he played at Indiana, my favorite basketball school. KAT because he is from New Jersey, and because he might be the best three-point shooting big in the game while still doing the dirty work in the paint. A two-way wing and a skilled big who can shoot. I knew the shape of the team I wanted before the front office did.

When the real Knicks traded for OG and then for KAT, I felt something strange, like watching a spec get implemented by someone else. I had foreseen those pieces. What I did not foresee was the engine that actually drives this title: the Villanova core, Jalen Brunson and Josh Hart and Mikal Bridges, a group of guys who already knew how to win together before they got here. That part reality wrote better than I did.

And hats off to Leon Rose, because the real credit belongs to him. While I was running simulations, he was doing the actual thing. A quiet former agent took over a franchise that had been a punchline and built this deliberately, one move at a time, Brunson and then Hart and then OG and then Bridges and then KAT, without ever mortgaging the future for a splash. I admire builders, and he is the builder here. It was something to watch an idea I had only ever run in a simulation get implemented for real, and then extended past anything I drew up, all the way to a title.

Which is the whole lesson, and the one place this touches the day job. I build systems for a living, long-horizon ones, and the way you do it is patient and deliberate, no shortcuts, the pieces assembled over years. You spec what you can foresee. OG and KAT were the parts I could see coming. But the best outcomes always arrive with something you did not script, and the discipline is to leave room for it instead of forcing your old plan over the better one in front of you. I had a plan for thirty years. The version that won was partly mine and partly a gift.

Goodbye to the waiting#

So the wait is over. Fifty-three years, answered. Brunson and Hart and Bridges power it, OG and KAT anchor it, and a franchise that spent my entire life as a lesson in patience finally paid the patience back.

I keep looking at the Willis Reed ball on the shelf. The promise on it came due. My grandfather handed me a team and a way of waiting for it, and tonight both of those finally make sense. Patience is not passive. It is the longest game there is, and the Knicks just won it.

Goodbye to the waiting. Hello, champions.

Keep reading

Post

Composite What You Trust, Watch What You Don't: A Trust Boundary for Data With Money Attached

Every system that fuses signals into one consequential number has a fault line: the data you trust enough to composite into a grade versus the data you only trust enough to watch. How I drew that boundary in my personal finance engine, and how a test keeps it honest.

Read
Post

Hello Again, Opus

Four days after I said goodbye to Opus, an export-control directive pulled Fable 5 offline and the fallback became the workhorse again. What I shipped in the window, what it cost, and the model-tiering plan for when Fable comes back.

Read
Post

Ten days of June: the SDD velocity numbers, seven weeks in

In April I published one week of SDD production numbers. The same data trail rerun for June 1 through 10 shows the velocity curve: 309 PRs opened, 293 merged, about 185 production deploys, and one footnote about outrunning GitHub Actions' default limits.

Read
Post

Autonomy is mostly knowing when to stop

I handed a backlog to Claude Fable, told it once it could merge, and let it run. It shipped seventeen items across five repos. The line that mattered was not in the work it finished. It was in the work it refused to touch.

Read
Post

How to backtest without fooling yourself

A backtest's job is not to find an edge. It is to stop you from believing in one that is not there. The toolkit I used to test my own trading engine, and the part where it killed my single best signal.

Read
Post

Goodbye Opus, Hello Fable

Anthropic shipped Claude Fable 5 and Mythos 5: same model, two names, one safeguard layer apart. What the new frontier model means for running agents in production.

Read
Written by Eric Caskey. I build AI tools you can actually use. Explore the Tools or see the case studies.