My daughter asked if developers used to write code by hand

Emma is eleven, and lately she's been doing what she calls "vibe coding" — basically telling AI what she wants and letting it do the heavy lifting. Something her parents could never have done at her age. But when she asked her dad "Did you guys actually write code with your hands?", there was a pause. The real curveball came next: "If AI writes for me, don't I learn nothing?".

That's the thing that makes you think. The question isn't whether the next generation will be less competent — the real question is whether "competence" even means the same thing anymore. Twenty years ago, a developer had to memorize syntax, know patterns, debug manually. Today AI does all that, and if you're good at prompt-writing, you get better results than someone who memorized the entire C++ manual.

It's not news that tools change work (the calculator did the same thing to mathematicians), but there's an interesting twist here: AI doesn't just replace execution, it replaces the entire way you think about a problem. When you write a good prompt, you're forced to articulate what you want — it's not laziness, it's a different skill. Maybe more useful than remembering where to put a semicolon.

Sure, the risk is real: if you don't understand what AI writes, eventually your app stops working when things get complicated. But Emma — and thousands of kids like her — aren't skipping the "knowing" part. They're skipping the "doing it manually by hand" to jump straight to "understanding it".

What surprised Emma's dad most? Not that she uses AI. It was that when he showed her badly-written AI code, she knew exactly what was wrong with it. Not because she'd memorized it, but because she'd spent time thinking about what she wanted things to do, not how to write them.