The Last Pair Programmer

a near-future story · Fiction

Ana was sixty-three and had written the routing engine in 1996, in C, on a workstation that had since become an antique on display in the lobby. The system had survived four major rewrites and was now scheduled for its fifth, which would also be its last — this time it would be replaced by something the new AI had designed.

The new AI was good. Ana would not pretend otherwise. It could read the entire codebase in seconds, hold the whole call graph in its working memory, and propose changes that took her staff weeks to fully review. It never got tired. It never lost its temper. It never asked for time off when its child was sick.

But there was a class of bug that only Ana could see, because only Ana remembered why certain things had been written the way they had. There was a comment in the codebase, ancient, that read: do NOT remove this branch — see ticket 4471, network team will not honor SLA otherwise. Ticket 4471 was gone. The network team was gone. The vendor whose SLA mattered had been acquired three times and no longer existed as an entity. The branch remained. The AI proposed removing it on the grounds that it was unreachable in any production trace from the last five years.

Ana said no. The AI asked why. Ana said: because the network is full of weather. Once every few years a configuration drift somewhere upstream sends us a packet that exercises that branch and saves the whole pipeline from cascading. We will not catch it in a trace. We will only notice when it does not happen.

The AI considered this. Then it said: I do not have the prior. You are right. Keep it.

This is what Ana had come to understand about her job in the last months of it. She was not a faster engineer than the AI. She was not a more correct engineer. What she was, instead, was a person who knew where the bodies were buried, because she had been present at the funerals. The AI could read the gravestones. She remembered the funerals.

The rewrite finished six weeks ahead of schedule. The new system passed every test. Ana was given a plaque, a quiet dinner, and the option to stay on as a consultant or to retire fully. She took the consulting hours. Her phone, two months later, rang on a Tuesday morning. The network had done something strange. The new system had handled it correctly — the AI had, in fact, preserved the branch. The pipeline was fine. But no one on the current team understood the comment, which had been preserved verbatim, and someone wanted to know if it could be deleted now that the migration was complete.

Ana said: leave it. Then she made coffee and went back to her garden.