WorkWritingAboutContactGet in touch
All writing
4 min read

I stopped writing code in 2015. I just shipped a platform.

The standard story says you go up the ladder and lose the keys to the codebase. Agents broke that trade. The bottleneck moved off typing and onto judgment, which is the one thing a decade of management actually sharpens.

The last production code I shipped was Scala, around 2015. After that I went up. More people, more countries, more org design, less keyboard. That is supposed to be the deal. You trade building for leading, you slowly lose the keys to the codebase, and one day you are the person in the room who can only point at things.

I made that trade on purpose. I don't regret it. But I never liked the part where the price was going quiet as a builder.

Over the last four months I built an internal platform. Solo. An engineering metrics system pulling Jira, GitHub, HiBob, and calendars into one view. An AI cost layer that attributes spend down to teams. A meeting transcriber with real encryption and identity. A showcase service, a skills marketplace, and the Terraform foundation underneath all of it. Not toys. Things people use.

I did not get younger or smarter. The bottleneck moved.

The scarce thing changed

For most of my career the scarce thing was typing. Knowing the syntax, holding the API in your head, grinding out the boilerplate, remembering where the bodies are buried in the build system. That is the muscle you lose first when you stop coding daily, and it is exactly the muscle that agents now rent to you for cents.

What they do not rent you is judgment. What to build and what to refuse. Where the real risk sits. Which "done" is actually done. Why a 403 leaks and a 404 doesn't. Whether the clean number on the dashboard is lying to you. That is the part a decade of management sharpens rather than dulls, because it is the part you have been doing in meetings the whole time.

So the leader-who-stopped-coding turns out to be carrying the half of the job that got more valuable, and renting back the half that got cheap.

An assembly line from idea to ships. Work tokens fly through the TYPING station, where a little robot labeled 'the agent, 0.3s' does the work, then pile up and jam at the JUDGMENT station, where a stick figure labeled 'you, still thinking' stands with a question mark over its head. A dashed arrow arcs from the 2015 typing station to the 2026 judgment station, labeled 'the bottleneck moved.' Footer: typing got cheap, judgment didn't.An assembly line from idea to ships. Work tokens fly through the TYPING station, where a little robot labeled 'the agent, 0.3s' does the work, then pile up and jam at the JUDGMENT station, where a stick figure labeled 'you, still thinking' stands with a question mark over its head. A dashed arrow arcs from the 2015 typing station to the 2026 judgment station, labeled 'the bottleneck moved.' Footer: typing got cheap, judgment didn't.
The work didn't get smaller. The jam just moved, from your keyboard to your judgment.

What it changed about the job

I can now prototype the thing I am about to ask a team to build. In an evening. So I walk in with a running artifact instead of a slide, and the conversation stops being about whether it is possible and starts being about whether it is right.

I argue from artifacts now. That is the whole shift. "Here is the thing, here is what it cost, here is where it broke" beats any amount of confident hand-waving, including my own. I have killed several of my own ideas this way, faster and with less ego, because the artifact embarrassed them before a person had to.

A balance scale. On the high, losing side sits a slide deck puffing out fading buzzwords - 'synergy', 'north star', 'Q3 vision', 'alignment', 'trust me', 'let's circle back' - labeled 'the deck, just trust me'. On the low, winning side sits a small terminal window printing '$ ./ship --it' with a blinking cursor and an orange '✓ it runs', labeled 'the running thing'. Footer: one of these you can run.A balance scale. On the high, losing side sits a slide deck puffing out fading buzzwords - 'synergy', 'north star', 'Q3 vision', 'alignment', 'trust me', 'let's circle back' - labeled 'the deck, just trust me'. On the low, winning side sits a small terminal window printing '$ ./ship --it' with a blinking cursor and an orange '✓ it runs', labeled 'the running thing'. Footer: one of these you can run.
A deck weighs nothing. A thing that runs settles the room before you finish the sentence.

What this is not

It is not "managers should all go back to coding full time." Your job is still the team. If you are heads-down in a worktree while your org drifts, you have optimized the wrong thing.

And it is not "you don't need engineers anymore." I built the parts I could specify. The engineers I work with build the parts that need someone living inside the problem for months, carrying context no spec captures. Those are different jobs. One did not eat the other.

The bottom line

The trade I made in 2015 had a hidden clause that just got rewritten. You can go up and keep the keys now. Not to ship the production system yourself, that is still the team's, but to stay fluent, to test your own ideas before you spend other people's time on them, and to stop arguing from vibes.

A leader who can still build, now that building is cheap, has an unfair advantage. Use it on your own ideas first. They deserve the scrutiny most.

Back to all writing