Technology. Aviation. Endurance. And whisky.

Long runs are where the hard problems come loose. The first hour belongs to the body; after that the mind is free to turn over whatever the desk could not resolve. Debugging works the same way: force rarely helps, distance does, and what surfaces is usually not the fix but the wrong assumption underneath it.

The cockpit teaches the stricter version. Fly the aeroplane first, and the right problem shows itself in the time that buys. Running offers the same time without the altitude, by removing every option except patience. Which here is not a virtue but a technique, and the one that separates a patch that works from an answer that is right.

Some decisions are only arithmetic, made once the facts are in. The ones that matter come earlier, when waiting for certainty costs more than being wrong. Across flying, ultrarunning, building software, and tasting whisky, the same problem keeps appearing in different clothes: how to act on incomplete information, and how much margin to leave for the gap.

Weather is a probability dressed as a fact; a race is a bet placed hours before it pays out; code that compiles is not code that is correct; a cask is a decision no one tastes for decades. What the four teach is not courage but a better relationship with uncertainty: how much room to keep for being wrong.

My mind is always ahead of the moment. I notice things before I can explain them — patterns, connections, details that don't sit right. Writing is how I bring order to that. Not to share conclusions, but to make the thought sit still long enough to examine it.

The four domains I move through — code, flight, distance, whisky — all demand decisions with incomplete information and refinement without a clear endpoint. They suit the way my mind works. The cost of noticing everything is that you cannot stop. It is useful. It is also, sometimes, exhausting. But it is the only way I know how to be.