I hand-write 0% of my code. I miss it.

I've been writing code for about 20 years. Today I hand-write it 0% of the time.

That's not a complaint. I'm excited about building with AI. It's the most leverage I've ever had. But most people skip past something in the rush to talk about productivity, and I want to say it plainly: I miss it.

If you spent years hand-crafting code, you might feel it too. So let's say it out loud first, before we get to the bright side.

What I actually miss

It's not the typing. It's what the typing was attached to.

The late nights deep in one hard problem, where the rest of the world fell away and it was just me and the thing I was trying to make work. The never-ending journey of learning to program: not memorizing syntax, but really understanding why things behaved the way they did under the hood. Building a complex system by hand, piece by piece, holding the whole shape of it in my head.

That work spoke to a technical and creative part of my brain at the same time. It was hard in a way I liked. Pretending I don't miss that would be dishonest.

So I'm not going to pretend. I do miss it.

On the bright side

Here's what I had to sit with.

The thing I was always reaching for didn't change at all. I still want to take a vision and turn it into something people use. I want to ship. I want to build a business. None of that went anywhere.

What changed is the leverage. The distance between "idea in my head" and "thing in customers' hands" just collapsed. The end I cared about is now massively more achievable than it was when I was hand-typing every line.

So my craft didn't die. It moved up a level.

Where the energy goes now

If the technical-creative part of my brain isn't getting fed by hand-writing code anymore, where does it go?

It turns out there's more than enough to do.

That same side of the brain, the part that loved understanding how the system worked and building it deliberately, now goes into designing the systems I build with. The agents. The workflows. The guardrails and the structure that let me build and ship products and tools and automations with AI at a professional level instead of just poking at a chat box and hoping.

That's not less technical. In a lot of ways it's harder. You're not solving one problem in one file anymore. You're designing the thing that solves whole classes of problems for you, reliably, over and over. It pulls on the exact same technical-creative muscle I built over 20 years. It just attaches it to a much bigger lever.

And I'll admit: it's a more rewarding use of that muscle than I expected.

The craft didn't die. It moved up a level.

That's the reframe that got me past the missing.

I'm not mourning a skill that's gone. I'm watching a skill move up a rung, from writing the code to designing the systems that write it. The craft is still craft. The creativity is still creativity. The technical depth still matters, maybe more than ever.

If you built your identity around hand-crafting software, you don't have to throw that away. You get to repoint it. The part you actually loved is still there waiting for you: the hard problem, the deliberate build, the system held in your head. It just moved up a level.

That's the work I'm teaching now. If you want to come along, that's what Builder Methods is for.