Ramblings of an aging IT geek
← Ramblings of an aging IT geek
personal

four hours of motorway and one episode that stuck

A long solo drive, a single podcast episode that ran the whole way, and why I've stopped trying to make car time productive.

Coffee and books on a table

I drove a long way at the weekend. Not for any grand reason, just family that needed visiting and a calendar that finally lined up. Four hours each way, most of it motorway, the kind of drive where the satnav stops being useful after the first junction and you're just following the same three lanes for a very long time.

I used to treat that time as a problem to be solved. Audiobook queued, a backlog of talks I'd been meaning to "catch up on", maybe a language app shouting verbs at me. Self-improvement at 70mph. It never worked. I'd arrive having absorbed nothing, vaguely annoyed that I'd wasted the slot.

This time I put on one podcast episode and let it run. No agenda, no learning outcome. Just two people talking about something they clearly loved, at length, with the sort of detail you only get when nobody's worried about the runtime.

A wide open landscape

And it was lovely. The bit that stuck with me was a tangent, of course, about how the host had spent two years restoring an old motorbike and got the whole thing running before realising he'd never actually learned to ride one. He talked about it the way good engineers talk about a side project that quietly took over their life: a little embarrassed, completely unrepentant. I laughed out loud somewhere around Stoke.

There's a thing that happens on a long drive once you stop fighting it. The road takes just enough of your attention that the fidgety part of your brain goes quiet. You can't check your phone, you can't open a second tab, you can't do the dozen small evasions that normally stop you from thinking about anything for more than ninety seconds. So you think. Or you don't, and you just listen, and that turns out to be fine too.

I've spent a lot of my career optimising things. Build times, query plans, the path from "idea" to "running in production". It's a good instinct in the right place. But I've slowly realised I apply it to bits of life that don't want optimising, and the drive is one of them. The point of the four hours isn't to extract maximum value per mile. The point is that you arrive, and on the way you got to be a person who isn't doing anything in particular.

I got home late, tired in the good way, with nothing to show for the journey except a podcast recommendation I've already passed to two people and a quiet resolve to do the long drive more often. Not productively. Just gladly.