What a 10-Year-Old Should Actually Know Before Python

Parents write to us with a quiet panic: is my ten-year-old “behind” because they have not done Python? Or “ahead” because they finished a Scratch course? Both questions assume the wrong unit. The unit is not hours of content. It is whether they can hold a small system in their head.

“Behind” in this market usually means they missed a brand. “Ahead” usually means they finished a playlist. Neither tells us if they can keep three steps in order when the bee appears. That is the only placement question that matters on the intro call.

Here is what we actually look for before we put a child in front of Python in a live class. None of it requires a previous academy. All of it can be checked in an intro conversation and a first session.

The four sentences

• Sequence: they can tell you what happens first, next, and last in a game they like.
• Loop: they can point to something that repeats — a jump, a score, a bee that keeps coming — and say so in ordinary words.
• Branch: they know that something different should happen if they hit the wall, or pick the other door.
• Honesty: when it does not work, they will look at the screen instead of looking at you to press the next button.

We do not administer a written exam. We ask them to narrate. Tell me the game. What repeats? What is different if you lose a life? If those answers come, Python is a typing problem, and typing problems are solvable in a room of four. If they cannot narrate, we do not punish them with syntax. We teach the sentences first — still First Code, still a project, still live.

Keyboard comfort helps. English or Arabic for the explanation is fine; the code will be English because the field is. We do not require touch-typing. We do require that they are willing to type. A child who will only tap a tablet will struggle here. The machine they are joining speaks in keys.

If they can say the steps, they can learn to type the steps. That is the gate. Not a certificate.

The first Python week

If they are ready, week one is not a language tour. It is one behaviour: a character moves, or a score goes up, or a question branches. They write it. It breaks. They read the line the mentor points at. That is the week. We do not cover lists, files, and “intro to AI” because a brochure had a column to fill.

A parent can check the week without knowing Python. Ask: what did you make? What broke? What did you change? If the child can answer those three, the class is working. If the answer is a platform name, it is not.

What we do not require

We do not require a year of another platform. We do not require that they have “done AI.” We do not require that they are “gifted.” We do require that a parent is not hoping the class will babysit. Four children and one mentor is a studio, not a waiting room.

We also do not require that they already love computers. Plenty of ten-year-olds love football, drawing, or stories. Those are better raw material than a child who has been praised for finishing modules. Curiosity about how a thing happened will carry them. A streak of completed videos will not.

If those four sentences are not there yet, First Code still has a place: we teach the sentences, then we type. If they are already there, we do not make them earn a badge in a language they have outgrown. We start the project. That is the whole placement policy. It fits in an intro call.