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

the one television show that gets the on-call dread right

A long-overdue rewatch of Halt and Catch Fire, and why it captures the texture of working in tech better than anything that puts a hacker in a hoodie.

Coffee and books on a desk

Most television about people who work with computers is unwatchable for anyone who actually works with computers. The screens are nonsense, the typing is theatrical, and someone always says "I'm in" with a straight face. I've made peace with it the way you make peace with weather. And then occasionally something comes along that gets it so right it's almost uncomfortable, and for me that show is Halt and Catch Fire. I finished a full rewatch last week, and it has aged into something even better than I remembered.

On paper it's a period drama about the early PC clone wars, then the rise of online services, told over four seasons across the eighties and into the nineties. What it's actually about is the specific, grinding, exhilarating experience of building things with other people, and how that builds you and wears you down in equal measure. That's the part nobody else seems to film.

the thing it understands about the work

The show knows that the technology is almost never the hard part. The hard part is the people, the timing, and the gap between the thing you imagined and the thing you can actually ship. There's a season where a small team builds something genuinely ahead of its time, and it doesn't matter, because the market isn't there yet and the company can't survive long enough to be early-but-right. Anyone who has shipped something good into an indifferent room will feel that in their teeth.

It also understands obsolescence in a way that stings. A character pours themselves into a piece of software, and the industry moves, and the thing becomes a footnote. Not because it was bad. Because that's what happens. Most of what we build is going to be turned off, migrated away from, or quietly forgotten, and the show treats that as the cost of the work rather than a tragedy. I found that oddly consoling. I've turned off services I was proud of. I've watched my own clever solutions become someone else's "why on earth did they do it this way".

A quiet landscape view

the on-call dread, before on-call had a name

There's no pager in the show, no PagerDuty, no Slack at three in the morning. But the dread is identical. The scene where something is about to go live and you can see, in the lead's face, the precise weight of "this could go badly and it will be mine when it does", that's on-call. That's the night before a migration. That's the deploy you talked yourself into on a Friday. The era is different and the feeling is exact.

What it gets right is that the dread and the love are the same circuit. You don't agonise over things you don't care about. The character who can't sleep before the launch is the same character who can't stop building. I recognise that person. I've been that person, on smaller stakes, with worse hardware, and the show treats it with a seriousness our profession rarely affords itself on screen.

why I keep coming back to it

A few reasons. It refuses to make anyone a genius who is right about everything; every one of them is brilliant and wrong by turns, which is the truest thing about working with talented people. It lets women be the engineers and the founders without making a speech about it. And it understands partnership, the working kind, the way two people can build something neither could alone and resent each other for needing the other to do it.

There's a relationship at the centre of the later seasons, two people who are better at the work because of each other and worse at almost everything else, and it's the most accurate depiction of a long technical collaboration I've seen. The pairing that produces your best work and your worst arguments. If you've had a proper engineering partnership, the kind where you finish each other's sentences in a design review and then don't speak for a fortnight, you'll know exactly what I mean.

I won't pretend it's a perfect show. It takes a season to find itself, and the early episodes lean harder on the hardware-heist plotting than they need to. Push through. By the time it settles into being about the people it's quietly one of the best things made about this industry, precisely because it stops being about the industry and starts being about the people stuck inside it.

It's not on right now, which is a shame, and I suspect it'll remain one of those shows people press on each other one at a time rather than something everyone watched. That feels appropriate. It's a show about building things that deserved more attention than they got, and it didn't get the attention it deserved either. Go and watch it. Then come and find me, and we'll argue about which season was the best, which is itself a very on-brand way to spend an evening.