The best thing I can leave my kids is the ability to build

When I was starting out, a hard-won technical skill could carry you for a decade or more. You learned a trade, a stack, a way of doing things, and that investment paid out for a long time. That deal is quietly expiring. The specific how of almost everything is being automated, abstracted, or made obsolete faster than you can master it. If I raised my kids to bet their futures on being the best in the room at some particular technique, I'd be training them for a race whose finish line keeps moving.

So the question I keep turning over is: what actually compounds? What's the thing that's worth more in twenty years, not less? And the honest answer I keep landing on is not a skill at all. It's a disposition — the reflex to treat a problem as something you can take apart and rebuild, plus enough range across tools that you're never fully dependent on any one of them staying relevant.

Don't optimize your kids for the skill that pays today. Optimize them for the ability to acquire the next skill faster than the last one decays.

I'm not making this case from the outside. I spent years carrying a sample bag as a medical-device rep, and I taught myself to build software sideways — not in any order a curriculum would design, but one problem at a time, because a spreadsheet had quietly outgrown being a spreadsheet. Nobody credentialed me into it. The skill I earn my living with today is not the one I started with, and it won't be the one I finish with either. That isn't a cautionary tale about a rocky path. It's the argument itself: I crossed that gap once, slowly, in a world with worse bridges than the one my kids will inherit.

What actually carried across wasn't any particular language or framework — those turned over two or three times while I wasn't looking. What carried across was the willingness to be a beginner on purpose, repeatedly, without it feeling like an emergency. That's the muscle I want them to build early. A kid who has done it even once — picked up something genuinely hard, been visibly bad at it, and stayed anyway — knows in their body that the distance between not-knowing and knowing is a distance you can walk. Everything downstream of that conviction is just reps.

There's a temptation, especially once you can afford it, to hand your kids the polished version of everything — the finished app, the sealed device, the experience engineered so nothing can go wrong and nothing can be taken apart. It's frictionless, and frictionless is exactly the problem. A thing you can't open is a thing that teaches you it's not yours to understand. Enough of those and you've quietly raised a very comfortable consumer who assumes the interesting parts of the world are somebody else's job.

The alternative isn't to deny them anything nice. It's to make sure a real fraction of what's around them is openable — breakable, fixable, modifiable, theirs to mess with. I'd rather they grow up with a few things they built badly than a lot of things they only ever used. The badly-built thing carries a lesson the polished one can't: that the line between user and maker is not a wall, it's a door, and the door opens from their side.

The reason this feels urgent rather than nostalgic is that the tools have crossed a threshold. Building something real used to require a long apprenticeship before you could make anything worth keeping — years between the wish and the working thing. That gap is collapsing. A motivated person with today's tools can go from idea to a working version faster than at any point in history, and the trajectory is still steepening. My kids are going to grow up on the far side of that collapse, where the binding constraint on making something is no longer skill but nerve and taste.

Which means the highest-leverage things I can give them are the two things the tools can't: the nerve to start something they don't yet know how to finish, and the taste to tell the difference between a thing worth building and a thing that just can be. Nerve and taste don't come from a course. They come from watching someone they trust do it in front of them, badly and then better, and being handed the keyboard.

There's a quieter thing I'm trying to model, and it's baked into how I build rather than into anything I say out loud. Almost every system I run is designed to make being wrong cheap. A deploy that snapshots itself before it touches anything and rolls back the moment a check fails. A command that runs as a dry run first and shows you exactly what it would do before it does it. The pattern underneath all of it is the same one: make the undo exist the instant the change does, so that trying something is never a bet you can't take back.

That isn't only an engineering habit; it's the exact thing I want my kids to feel about the world. Being stuck is safe. Being wrong is recoverable, and usually informative. The reason a person freezes in front of a hard problem is almost never a shortage of ability — it's the fear that a mistake is permanent and public. If I can give them a childhood where the undo button is always within reach, where you can open the thing and break it and put it back, then the nerve I keep insisting matters most stops being a personality trait they either have or don't. It becomes the rational response to an environment where trying is cheap.

So when I think about what I'm actually building — the command center, the network of sites, the whole apparatus — part of it is a working demonstration I get to run in front of my kids. Not "look what your dad made," but "look, this is a thing one person can do now, and the door is right here." The systems are the visible output. The real product is a house where the default assumption is that the world is buildable, and the people in it are the ones who build it.

I can't leave my kids a guarantee about which skills will matter, because I genuinely don't know, and anyone who claims to is selling something. What I can leave them is a stance: that a problem is an invitation, that a tool is something you can pick up and eventually make, and that being stuck is the beginning of building rather than the end of trying. Inheritance, it turns out, is a verb. It's not the finished thing I pass down. It's the capacity to make the next one — and that's the only bequest I can think of whose value goes up as everything else's goes down.