You remember your first line of code. It wasn’t in a brightly colored sandbox with drag-and-drop blocks. It was messy. It was confusing. It was friction.
Recently, John Carmack asked a dangerous question on Twitter: Has early Scratch experience actually led to fulfilling careers? The replies were a masterclass in what we get wrong about tech education.
One commenter nailed it. They took a C++ class at 13, but when asked what got them into tech, they didn’t cite the class. They credited scripting RuneScape bots. “Because I had fun and it was mine.” Another started on Scratch, moved to Minecraft, and 15 years later is designing jigs in parametric CAD for space lasers.
We obsess over building the perfect on-ramp, but we completely abandon the bridge.
Look at Scratch. It’s designed to be frictionless. High abstraction, child-friendly UX, colorful blocks. It’s perfect for day one. But children learn fast. Eventually, they outgrow the training wheels. They reach the edge of the sandbox and look out into the vast desert of real-world programming. And there’s nothing there to guide them across.
The very design that makes Scratch accessible is what creates the desert that prevents users from transitioning to advanced programming. You don’t become a software engineer by dragging blocks. You become one by fighting with a compiler at 2 AM because your RuneScape bot keeps crashing.
Friction isn’t the enemy of learning; it’s the catalyst of mastery.
As educators, parents, and tech professionals, we panic over initial exposure. We think if we just make coding fun and easy, they’ll stick with it. But initial exposure doesn’t equal retention. The true catalyst isn’t the first moment of low-friction exploration. It’s the first moment of unstructured friction where a user builds something they actually care about.
It’s the RS bot that farms gold while you’re at school. It’s the Minecraft mod that lets you spawn a thousand creepers. It’s the crappy 4K BASIC program that barely runs but is entirely yours.
We are equipping the next generation with training wheels they will never take off. We give them the sandbox, but we don’t give them the shovel to dig their way out.
You don’t fall in love with programming because it’s easy. You fall in love because it lets you build the things you actually care about.
If we want to build the next generation of engineers, we have to stop obsessing over the on-ramp and start building the bridge. We need ecosystems that support purposeful, messy, frustrating creation. Because that’s where the magic happens.
FAQ
Q: But doesn't Scratch teach logic? Isn't that the point?
A: Yes, it teaches logic, but logic without syntax or ecosystem support is a dead end. You don't become a mechanic by playing with Hot Wheels.
Q: So what should educators do differently?
A: Stop focusing entirely on frictionless entry. Design 'bridges'—ecosystems where simple scripts can evolve into real-world projects, like modding communities or simple APIs.
Q: Are you saying Scratch is bad?
A: No, Scratch is a great toy. The problem is treating it as the foundation of a career. It's an on-ramp with no bridge to the highway.