This week I spent fifteen minutes finding a bug.
Records were dropping out of a data pipeline somewhere between where they started and where they were supposed to land, and nobody could say where. Finding it meant tracing the path through somewhere between twelve and fifteen thousand lines of code.
I could do that by hand. It would take days. Instead I put an AI tool on it, worked through it with the thing, and had the answer before my coffee got cold.
In 2003 I did not know what SQL stood for. I could not have told you what a data pipeline was, because the phrase wasn’t in general use. Artificial intelligence was something from The Matrix — machines that were coming to take over, not something that would help you find a dropped record on a Tuesday.
My title has the word “data” in it. The job is mostly defining the rules for how a system is supposed to work and then governing it by building consensus with people — running the state of the data about the way you’d run the state of a country. It is not a glamorous line of work. I’d have to look up when a job like it first existed anywhere.
I’ve spent a lot of this year saying nobody ever laid the path out for me. Not at the church, not at the gallery, not in the wilderness stretch after.
But I don’t think anybody could have laid this one out.
There was no one in 2003 who could have looked at a twenty-five-year-old with a sociology degree and pointed him at a job that didn’t exist, using tools nobody had built, in a role that wouldn’t exist for another decade. The people around me then couldn’t have gotten here either. It wasn’t a place yet.
A map to a known destination is geography. A map to an unknown one is prognostication, and nobody owed me that.
Except I keep thinking about Randy.
Randy was an adjuster at a place I worked in my twenties. He’s the reason I got that job — he knew they needed somebody and he put my name in.
I was the most computer-literate person in that building, which tells you more about the building than about me. So Randy would come to me with questions. Do I left click or right click? I’d tell him. Next time, same question.
I was still answering that question ten years later.
I loved that old man. He was good people, and I mean that. But somewhere in there I remember thinking, buddy, at some point you have to learn how to click your mouse.
He had the thing I say I never got. Somebody right there, patient, glad to help, for ten years. He just never asked a question big enough to take him anywhere.
So it’s two things at once, and I’ve been saying one of them.
Nobody could have mapped me to this job. That part is true and I’m going to stop treating it as a grievance.
But the terrain under my feet was always well understood by somebody. Why a gallery calls the people who already bought from it. What the volunteers at that church were actually offering me. What an editor does. None of that required foresight. It was ordinary knowledge, sitting in the room, that I either wasn’t given or didn’t know how to ask for.
I don’t know how to tell which of those it was, from here.
The twenty-five-year-old wanted to write songs for a living.
He’d be disappointed by the office. Not by the problem-solving — he’d have liked that part, he always liked figuring out what was broken. But the fact of an office, every day, doing something with a title he couldn’t have parsed.
He’d have been wrong about the songs, though. I’ve got an album out. Eleven tracks, written and recorded and released, in a year when the day job was going fine.
Nobody mapped that either.



