Your Child Is World-Building, Not Messing About

Last updated: September 2026

A child learning to code will keep turning the code into a story, and most adults read that as drifting off task. It is the opposite. It is the strongest engagement signal you get, and if you teach against it you spend the rest of the year fighting the only thing keeping them in the chair.

I watched this happen three times in three consecutive lessons with the same 8-year-old, and by the third I had stopped thinking of it as a tangent.

The spinning cat

In his first session we built a character that moved across the screen. Because of how the blocks were arranged, it also rotated as it went, which looked wrong. An adult sees a bug.

He did not. He said the character was climbing, because mountains go higher every time you walk. The spin was the effort of the climb.

That is not a child avoiding the problem. That is a child taking an unexplained behaviour, building a model that accounts for it, and making the model interesting enough to keep going. He then wanted to make the mountain steeper, which meant changing a number, which meant learning what the number did.

A week later, a character stuck at the centre of the screen became someone who needed a companion running alongside them. Another week after that, a creature crossing a desert prompted a genuine question about whether that animal could survive there, since it lives on beaches and beaches are hot.

Three sessions, three completely different worlds, all of them arriving unprompted out of a mechanical detail.

He also rejected a world that did not make sense

The part that convinced me this was not just play happened early on. I had put a cat on a seaside backdrop, and he objected. A cat does not belong next to water.

He was not being difficult. He was applying a consistency rule to a world he was building, and my sloppy choice had broken it. That is a designer's instinct, and it showed up before he could write a single line of Python.

"Best part is showing something, then letting you try it before explaining again. Unlike group lessons where you just copy, this method makes things click and helps you understand deeply." Anthony, parent of a 12-year-old learning Python

Things click when a child has a reason to want them to click. The world is the reason.

Why this matters more than it looks

Children abandon coding when it stops meaning anything. Not when it gets hard, when it gets pointless. A loop that makes a number go up is arithmetic homework. A loop that makes a crab cross a desert is a story with a mechanism underneath it, and the mechanism is the same loop.

The story is not a reward for doing the work. It is what makes the work worth doing.

Across 200+ kids I have taught, the ones who keep going past the first frustrating month are almost always the ones building something they can describe to another person. Not the ones with the best grasp of syntax. The ones who can tell you what their thing is about.

What this looks like when you get it wrong

The failure mode is subtle, because it does not look like a failure. You redirect. The child says the character is falling off a mountain and you say yes, but look, the reason it is spinning is that the turn block is inside the forever loop, and now let us fix that.

Everything in that sentence is true and useful. It also just told a child that their idea was an interruption to the real lesson.

Do it enough times and they stop offering. What you get instead is a compliant student who waits to be told what to build, which is a much worse position to teach from, and one that is genuinely hard to reverse. I would rather spend four minutes on a mountain that does not exist.

What to do instead

Take the world seriously first, then attach the mechanism to it. When he said the character was climbing, the useful move was to ask how we could make it climb faster, because that question has a block behind it.

You do not need to understand the code to do this at home. When your child tells you what is happening on screen, ask what happens next in the story, then ask what they would need to change to make that happen. The second question quietly turns a narrative into a specification, which is what programming actually is.

And when the world stops making sense, say so. He was right about the cat and the water. Being held to consistency is part of the game, and children like it more than they like being humoured.

If your child is at the stage where none of this has started yet, what your child actually learns in Scratch covers the early sequence, and how to get your child interested in coding covers building the interest in the first place.

Frequently Asked Questions

My child spends more time on the story than the code. Is that a problem? Not at an early stage. The story is what sustains attention across the months where the code is still tedious. It becomes a problem only if nothing ever gets built, and the fix for that is a small deadline on a working version, not removing the story.

Should I steer them toward more serious projects? No. Seriousness is not what produces skill, repetition is, and children repeat what they care about. A silly project finished teaches more than a serious project abandoned.

How do I tell world-building from avoidance? Ask what they would need to change to make the next bit happen. A child who is building can usually answer, even roughly. A child who is avoiding the work changes the subject.

The Bottom Line

When a child turns a rotating sprite into someone climbing a mountain, they have not left the lesson. They have found the reason to stay in it.

Teach into the world rather than around it, and the mechanics arrive on their own, because a child who wants the mountain steeper will learn what the number does.

I teach kids ages 8 to 16 online, 1-on-1, and building lessons around what a child is already imagining is most of why they keep turning up. Book a free Discovery Call.