A Weekend Thought

I learned by digging. A problem would sit in front of me and I’d stay with it — get it wrong, back up, try a different way. The thing that came out at the end had the shape of all that struggle in it. That’s how the instinct formed. Not from reading, not from being told. From being wrong in enough different ways.

That’s how it worked for a long time.

Now I describe a problem and a solution appears. I adjust it, wire it in, move on. The thing gets built — that part is real. But somewhere in there the struggle went quiet, and I’m not sure what’s forming in its place. I don’t know if I’m still learning or just moving faster.

I don’t know if the old way still matters. Maybe it was never about the difficulty — maybe it was always about what got made. Maybe the friction was just friction.

This has happened before. High-level languages abstracted away memory management. IDEs abstracted away the compiler. The web abstracted away the machine. Each time, the field moved and people found their footing — differently, but they found it.

But I keep coming back to a question I can’t answer. What does learning to code look like in five years? When you onboard someone onto a project, what do you actually walk them through — the codebase, or the prompts? What does it even mean to understand a system you didn’t write and neither did anyone on your team?

I find myself genuinely curious — and a little unsettled — about what that first day looks like for someone just starting out. And quietly uncertain about what it looks like for me, too.