My dad used to have a workbench in the garage. Clean. Organized. Every screwdriver in its place, every drawer labeled. A bench vise bolted to the edge, the kind with the big screw handle you crank to clamp things down. As a kid I thought that was the most impressive thing in the house. Not because I understood what any of it was for. Just because he clearly did.
He's moved since. The workbench is gone.
He could fix anything. Plumbing, electrical, the fence. He'd look at something broken, think for a minute, and then go get the right tool. I'd hand him things and try to follow what was happening.
I never really learned it. Not properly. I picked up enough to hang a shelf, but if something breaks in the house I'm calling someone. I don't have his hands.
He asked me once how the internet actually works. Not philosophically. Technically. How does a packet get from here to a server somewhere in Frankfurt and back in 11 milliseconds? I could draw the whole path from memory. DNS, TCP handshake, routing hops, load balancer, the lot.
He just nodded. Not because he didn't care. Because it wasn't his world.
I built my first PC with my uncle. He helped me pick the parts. I was maybe 14, and there was no "just buy one." You went to the store with a list and a budget and you figured out what fit together. Which RAM your motherboard actually supported. Whether the GPU would physically fit in the case. If it didn't, you needed a bigger case, which meant a different power supply, which meant going back to the list.
My uncle knew this stuff. He walked me through it. We spent an afternoon on it. Half the time was just cable management and making sure I wasn't forcing things into slots they didn't belong in.
When it posted for the first time I felt like I'd built something real. Because I had. I understood what was inside that box because there was no other way to get it running.
That's how I learned. Not from a class. From needing to.
My little brother opens his laptop and it works.
He's fast on it. Knows his way around apps and settings I'd have to dig for. He's comfortable in that world in a way that's native, not learned. But there's no reason he'd ever open the thing up. No reason he'd need to know what a BIOS is or why thermal paste matters. The machine just runs.
That's not a failing. Somebody built it well enough that he doesn't have to think about it. That's the whole point.
Same way I don't think about what's under the hood of a car.
I don't own a car right now. When I need one, I lease. The appeal is exactly what you'd expect: I don't want to maintain it. I don't want to diagnose it. I want to drive it and give it back.
I imagine that might be alien to my dad's generation. Why don't you change your own oil, replace brake pads in the driveway. That was just what they did. The idea of paying someone else for the privilege of not understanding your own vehicle would've made no sense to them at my age.
But I do it without thinking. Because the system around cars got good enough that I could opt out of understanding them. That's the trade.
That's the thing nobody talks about. The reason I don't know what a carburetor sounds like isn't because my dad's generation failed to teach mine. It's because they succeeded. They got so good at engines that they built ones that don't need you to listen anymore. You plug in a scanner, it spits out an OBD code, you replace the part. The skill didn't disappear. It got compressed into the machine. The diagnostic tool carries my dad's generation's knowledge so I don't have to.
That's what progress actually is. Not forgetting. Compression. Someone masters something so deeply that they build the thing that makes the mastery unnecessary. And then the next person just uses it.
I'm 33. I run infrastructure for a living. Containers, orchestration, systems that keep other systems running. I build platforms so reliable that the people using them never have to think about what's underneath.
That's the same thing my dad did. Different layer. Same act. I'm making my own knowledge unnecessary for whoever comes after me. That's not a side effect of what I do. That's the whole job.
Someday my kids will prompt an AI and it'll write the config file. They'll deploy something with a button that took me years to learn how to do by hand. They won't know what a prompt actually does under the surface. They won't need to. Because it will be built well enough that they don't have to.
And I'll try to explain how it works, and I'll get the same nod my dad gave me when I explained packet routing.
The workbench is gone. My dad moved. The tools are in boxes somewhere, or given away, or just gone.
But the knowledge that was on that bench is everywhere. It's in the walls of the house he built. In the car that starts without thinking about it. In every mechanism that just works because someone, once, understood it well enough to make it invisible.
Mastery's final act is making itself obsolete.
That's the price of progress. Not that we forget. That we succeed so completely at one layer that the next generation never needs to learn it. And the proof that it worked is that they don't even know what they're missing.