My daughter Emma is 11. She's been vibe coding lately, and honestly, she's pretty good at it.
The other day she looked over my shoulder at my IDE and asked: "Dad, was there ever a time when a developer had to write each one of those characters by hand?"
I said yeah, like six months ago.
It was her follow-up that gave me pause: "But how did you know what to write?"
I had to stop and think about it, because that question — how did you know what to write — was basically the entire profession. That was the craft. That was what I spent my career getting good at.
I started coding at six on a TRS-80. This was my first program:
10 PRINT "HELLO WORLD"
20 GOTO 10
Back then, kids' magazines printed BASIC programs in the back pages and you'd copy them character by character and run them. That's how a lot of us got hooked.
Then it got more powerful, more complex, and a lot harder to break into.
For most of my career, the standard loop was: write some code → hit a wall → Google it → find a StackOverflow answer → copy, paste, tweak. That ran from the late 90s to roughly 2022. Then everything changed.
I recently picked up woodworking as a hobby, and AI coding tools feel a lot like the moment power tools entered the shop. Does the circular saw replace the handsaw entirely? Does it just mean I build ten times as many birdhouses? Those questions are still unresolved for me.
What I do know is this: there has never been a better time to invite someone new into programming. The barrier that built up over decades is coming down fast.
If you're feeling scared by how fast things are moving, the best thing you can do is start building something. Anything. You might find it's a lot more fun than it is scary.
If this spoke to you, check out the full video here:
Top comments (4)
I think the scariest thought patterns we get caught up in as devs are to project growth on to part of the future and view another variable as static. We're not going to be producing the same amount of code with more input — we are seeing an explosion in code churn and the feedback loops created. Managing this feedback loop is a vital skill that rewards system thinking the same way coding always has.
Hey @greggyb. Hope you are having a good morning, afternoon, or evening!
This process felt like yesterday for me! I remember when it stopped around my undergraduate years when ChatGPT was first announce.
The process was fun because it enabled my brain to think critically. Nothing wrong with AI and I think it is a good tool. I just feel like we are relying it too much to the point where we can't even explain what the code does.
Compare to the old process, at least you were actively try to problem solve by search up documentation, reading other people's code, etc. For Vibe Coding, you just "trust".
Midway, I was writing an article on what @sylwia-lask posted, but going to reference this post as an addition! Thanks for sharing!! :D
That follow-up is sharper than it sounds. "How did you know what to write" was never really about the typing, it was knowing what to build, which tradeoffs matter, what "done" looks like. The keystrokes moved to the AI, but that judgment just relocated into the prompt. Your daughter basically pointed at the actual job and called it the easy part. 🙃
Ah, the good 'ole TRS-80. I remember those days well. Having a screen and keyboard was quite the upgrade from punch cards.