There is a certain type of parent who shows up to their child's first coding consultation and announces, with tremendous confidence: "She's only five, but she's gifted. She already sorts her toys by colour." And there is another type of parent who waits until their child is fourteen before asking — quietly, guiltily — "Is it too late?"
The honest answer to both is nuanced. No, a child who sorts toys by colour is not necessarily ready for coding lessons (though, to be fair, that's a kind of computational thinking). And no, fourteen is absolutely not too late. But the more useful question is not "when should my child learn to code?" It's "how do I know when they're ready?"
Readiness is not purely about age. Studies from the MIT Media Lab and the University of Edinburgh consistently show that the most reliable predictors of early coding success are behavioural — not chronological. Here are the eight signals to watch for.
The Eight Signs
There is a philosophical difference between a child who uses a TV remote and one who wonders how pressing a button sends a signal through the air to a box across the room. The second child has a disposition toward mechanisms — an itch for the why behind the what. That itch is the seed of computational thinking. Feed it.
Lego. Cardboard. Pots from the kitchen. Blankets arranged into architectural structures of questionable stability. Children who instinctively construct — who see raw materials and imagine outcomes — are rehearsing the most important skill in programming: turning an idea into a thing that works.
This is the one. A child who throws a tower of blocks across the room when it collapses is not yet ready for debugging at 10pm. A child who looks at the collapsed tower with a curious expression and repositions the base? That child is ready to code. Persistence in the face of failure isn't just useful in programming — it is programming.
Code is, at its heart, a sequence of instructions. A child who can follow: "go to your room, get your blue shoes, bring them to the kitchen, and put them by the door" — without losing a step — is already thinking sequentially. That's the architecture of every program ever written.
The child who finishes a video game level and immediately theorises about how the level was designed — who wonders what rules the designer wrote, what makes the collision detection work, how the enemy knows when to move — is thinking like a programmer before they've ever opened a laptop. The game, to them, is already code. They just need the language.
Pattern recognition is foundational to programming — loops, functions, and algorithms all emerge from recognising that something repeats. Children who notice patterns in music, in stories, in nature, in daily routines — and who apply those patterns deliberately in their own behaviour — are already halfway there. They just need someone to show them that code is patterns with superpowers.
Programming regularly confronts you with problems that have no immediately obvious solution. The ability to sit with that discomfort — even briefly — and think rather than panic is a remarkable indicator of readiness. You don't need them to be unflappable. You need them to be willing to try before giving up.
Motivation is everything. A child who wants to build something specific will move mountains to learn how. That sentence — "I want to make a game" — is a gift. If you've heard it recently, don't let it go cold. The window between genuine enthusiasm and distraction is fleeting.
What If They Show All Eight?
Start yesterday. Book the class. Put them in front of Scratch on a Saturday morning and watch what happens. Children who tick most or all of these boxes usually take to structured coding education with a kind of terrifying speed that will simultaneously fill you with pride and make you feel very old.
What If They Only Show Two or Three?
That's absolutely fine. The signs are not a gatekeeping test — they're a readiness indicator. A child with two or three strong signals and a good mentor will develop the others in a nurturing learning environment. In fact, many of our most successful students came in with nothing more than Signal 8: they just really wanted to make a game. Everything else followed.
The best time to start was six months ago. The second best time is the moment your child says "I want to build something."
A Note on Age
Since the question always comes: there is no universal age floor. We've taught students as young as five, successfully. We've also had seven-year-olds who weren't quite ready yet and eight-year-olds who were absolutely ready at six. The signals matter more than the birthday.
What is true is that children who begin with structured, 1-on-1 mentorship between the ages of 7 and 12 tend to make the fastest foundational progress. The brain at that stage is extraordinarily receptive to new logical frameworks, and the enthusiasm for creation is typically at its peak before the social anxieties of adolescence set in.
But again — none of this means that your thirteen-year-old is behind. It means your seven-year-old who just said "I want to build a game" might be exactly on time.