The Man Who Forgot How to Build

The email in Raj's drafts folder is a keynote he has not finished, and he is not going to finish it now.

KL606 has been in the air about two hours, out past the coast, the last of California gone under the wing and the enormous emptiness of the north beginning, the part of the map with almost nothing on it, ice and water and the thin idea of Greenland somewhere ahead. He is in seat 4A with a glass of orange juice he asked for instead of the wine, and his laptop is open, and the talk he is meant to be rehearsing is sitting there in a tab. Scaling Engineering Organizations. Ninety minutes, main stage, tomorrow morning, in a converted gasworks in Amsterdam, in front of something like fourteen hundred engineers who will file in with their lanyards and their coffees to hear him, Raj, explain how you take a team from twenty people to two thousand without it falling apart.

He is qualified to give the talk. That is not in question. He has done exactly that. He is a very senior man now, a title with the letter V in it, and the conference flew him business class and put him in a good hotel and printed his face on the program next to a paragraph that uses the word visionary, which made him wince when he first read it and winces him still.

What no one filing into that gasworks tomorrow will know is that Raj has not written a real line of code in three years, and that somewhere over the Pacific this afternoon he tried to, and could not.

He grew up with one machine. That is the whole origin of him, if you want it. A single old computer in a hot back room in a city he does not talk about much, a hand-me-down with a cracked case, and a boy who was supposed to be doing something else and instead taught himself, night after night, in the blue light, how to make it do things. The first program he ever wrote printed his own name across the screen, over and over, faster than the eye could follow, a waterfall of Raj Raj Raj, and he had made it, out of nothing, out of typed symbols, and he could not sleep that night for the joy of it. That is not an exaggeration for the sake of the story. He genuinely could not sleep. He was fourteen and he had discovered that he could reach into a machine and build a thing that had not existed in the universe five minutes before, and nothing anyone offered him for the rest of his life was ever quite as good as that.

He got good. He got very good. He crossed an ocean the first time for graduate school, terrified and broke, and he found the one country and the one industry that would pay a person simply to be excellent at the thing he already loved for free. He built. He built systems people used. He built the thing that, at his first real company, held the whole product up, the load-bearing wall, the part that only he fully understood, and he was proud of that in a way he could not fully explain to his parents on the phone. He was, for a stretch of years in his thirties, exactly where a human being is supposed to be, doing the thing he was made for, at the height of his powers, and being told he was wonderful for it.

And so, of course, they promoted him.

That is how it works. That is the only way it works. When someone is the best at the thing, the company does the natural thing, the sane-seeming thing, the thing that every company on earth does. It takes him off the thing. It makes him a lead, so his skill can be multiplied across others. Then a manager, so more others. Then a director, then the title with the V, each step a small and reasonable promotion, each one celebrated, each one accompanied by a raise that made the mortgage smaller and the children's schools better, and each one moving him one measured pace further from the keyboard and one pace closer to the calendar. Nobody did this to him cruelly. Everyone did it kindly. He said yes every time, because saying yes is what you do, because the ladder only goes one way, because at some point the money and the title become the way you know you are winning, and because there is no rung on the ladder labeled stay here, keep building, this is enough.

His days now are made of a substance he could not have imagined at fourteen. He goes from one video call to the next. He reviews roadmaps, which are documents in which people make promises about work they have not done yet. He sits in planning meetings where the promises are negotiated. He sits in status meetings where the promises are checked against reality and found wanting, and he carries the gap upward to people who made him promise it in the first place, and he carries the pressure back down to the people who have to actually do it. He does one-on-ones in which he tells young engineers who are exactly what he used to be that they are doing well and should think about, someday, a role like his. He is a manager of promises. He does not make things. He makes sure other people make things, and then he explains, to those above and below, why the things are late.

The worst part, the part he has never said out loud to anyone, is that he is jealous of his own team. He sits in a review and a twenty-six-year-old shows what she built over two weeks, some clean and clever thing, and it is good, and he says so, and inside him there is a small ugly ache that he is ashamed of, which is not that she did it badly but that she got to do it at all. She got to spend two weeks inside the problem, in the flow, in the blue light, and he got to spend two weeks in meetings about her two weeks. He goes to bed most nights having had, by every measure his calendar can see, a productive day, and having built precisely nothing.

So this afternoon, somewhere out over the cold water, instead of finishing the talk about scaling engineering organizations, Raj did a small and private thing. He closed the tab with the slides, and he opened a code editor, a clean empty file, and he decided he would just build something. Anything. A tiny toy, the kind of thing he could once do half-asleep. Just to feel it again. Just to remember.

The cursor blinked at him on the empty file.

And he sat there. He, who once held up an entire product in his head, sat in seat 4A and could not think of how to begin. It was not that his mind was blank. It was worse and more specific than that. The tools had moved. The language he reached for by muscle memory had grown three versions past him while he sat in rooms; the framework everyone used now was one he had only ever heard described in meetings, in the abstract, in the way you hear about a country you administer but have never walked in. He typed a few lines, the old way, his way, and even as he typed them he knew they were the lines of a man who had been away, dated, clumsy, the syntax of a fluent speaker who has not been home in years and can hear his own accent going wrong. The thing he had been the best in the world at, the thing that was not just his skill but his self, the reason he could not sleep at fourteen, had quietly moved on and left him behind, and it had happened not while he was failing but while he was succeeding, one kind reasonable promotion at a time.

He shut the laptop for a moment and looked out at the white nothing. He is forty-six years old. He is very well paid. His parents are proud in a way that took decades to earn. And he understands, at thirty-eight thousand feet with the drink going warm beside him, that he has been promoted out of his own life, and that the industry has a name for what happened to him, and the name is success.

Here is the thing he keeps circling, the thing that is almost angry in him now. It did not have to be a trade. Somewhere along the way the company decided that the only way to get more out of a great builder was to stop him building and set him to managing builders, that the coordination and the promises and the status and the herding had to be loaded onto its best people as the price of their growth, as if there were no other place for all of that weight to go. So it takes the person who loves the work most, and who is best at it, and it slowly, kindly, turns him into the person who no longer does it, and calls this a career. Multiply that by every company in this whole industry and you have a quiet catastrophe hiding inside a success story. All the great makers, one by one, promoted away from making, because the org had nowhere else to put the machinery of scale except on their backs.

He does not solve that tonight. You do not solve the shape of an entire industry over the Atlantic. But he does one more small thing, and it is the only thing on KL606 that matters. He opens the empty file again, and this time he does not try to build something impressive, nothing worthy of the man on the program with the word visionary next to his face. He types the simplest program there is, the first one, the one from the hot back room. He makes the machine print his own name. And it runs, clumsy syntax and all, and there it is on the screen in front of him at thirty-eight thousand feet, a little waterfall, Raj Raj Raj, faster than the eye can follow, a thing that did not exist in the universe five minutes ago, and for about ten seconds he is fourteen years old and completely, stupidly happy, and his eyes sting in a way he will blame on the dry cabin air if the man across the aisle happens to look over.

The plane begins its long descent into the Dutch morning, the grey-green flatness and the canals coming up like a diagram out of the cloud. Raj will give the talk. He is too professional not to. But he has decided two things somewhere over the ocean that he means to keep. The first is that he is going to find his way back to the empty file, even a little, even on a Sunday, even badly, because a man should not go to his grave having stopped doing the one thing that once kept him awake with joy. And the second, the one that will outlast the jet lag, is that he is going to stop doing to the twenty-six-year-old on his team what was so kindly done to him. He is going to find a way to let his best builders keep building, and to put the weight of all those promises somewhere other than on the backs of the only people who can actually make the thing. He does not fully know how yet. But for the first time in three years he wants to solve a problem again, and that, he thinks as the wheels reach for Amsterdam, is at least a beginning.

The North Atlantic Briefing is for the people who were promoted out of the work they loved because the company had nowhere else to put the weight of scale. If growing means turning your best makers into managers of other people's promises, a VDC Readiness Memo is a short, honest look at how to carry the coordination and delivery some other way, so the people who build get to keep building.