What “Learning to Code” Should Look Like at 7, 12 and 16

Most coding schools sell one promise to every parent: your child will “learn to code.” Then they run the same block puzzles at seven, twelve, and sixteen, and call it a pathway. That is not a school. That is a playlist.

A seven-year-old, a twelve-year-old, and a sixteen-year-old are not the same student with a different marketing badge. Their working memory is different. What they will sit still for is different. What they can explain to a parent is different. If the work does not change, the class is entertainment with a certificate.

We hear the same sentence from families in Dubai, Riyadh, Doha, and Kuwait City: they already did a course. Then we ask what they can open. Often the answer is a login, a badge, or a video of someone else’s demo. That is why we split the school into three programmes — not three prices for the same cartoon.

At Codeoko the loop stays the same at every age: understand, build, debug, show. The artefact does not. Below is what we actually mean when we say a child is learning to code — at 7, at 12, and at 16 — in live classes of four, on GST and AST evenings.

At 7: a game they can play tonight

First Code is not “computational thinking worksheets.” It is a 7–10 year-old writing steps in ordinary language, then typing those steps so a character moves, a score goes up, or a story branches. If they cannot play what they made, we are not done.

What they should be able to say, without a script: this happens first, then this, and if they hit the bee they lose a life. That sentence is the whole subject at this age. Syntax comes in service of it — Python, not a cartoon language they will have to unlearn — once the idea is in their mouth.

The hour is short on purpose. Live evenings, four children, one mentor. A seven-year-old will not hold a three-hour lecture. They will hold a bee, a score, and a mentor who waits until the lives are real. Arabic or English for the talking; English for the code, because that is the field. Parents do not need to sit in. They need something they can ask about on the sofa: press space. What happens?

What “done” looks like at seven

• A tiny game with a start, a choice, and an end.
• A drawing or story they can open on the family laptop.
• Twelve minutes of show-and-tell a parent can watch. No slides.

At 12: something a parent can open in a browser

App Builders (11–14) leave the sandbox. A page has to load. A jump has gravity. A test is allowed to go red for a real reason. This is the age where “I followed the tutorial” stops being a defence.

A twelve-year-old who can drag blocks but cannot say why the rover turned left is not ready for the next slogan. They are ready for a mentor who will break the work on purpose, then sit there while they find the line.

Two hours, twice a week, is enough to ship a small thing and still have time to fail it. The mentor’s second class in the week is not “more content.” It is: I tried to break what you built. Gravity is wrong. The link 404s. The test is green for the wrong reason. Now you fix it. That is the difference between a course and a studio.

• A personal site on their own machine — name, about, work.
• A Python game they wrote, not downloaded.
• At least one test that fails for the right reason.

At 16: a system they can pause

AI Engineers (15–18) is not a ChatGPT club. The brief is: train something small, show the number, and say what you would try next. A chatbot that answers from their notes. A camera that names a cup. A net that reads a digit. If they cannot explain where the answer came from, it is not theirs.

This is also when 1:1 is sometimes the honest recommendation — not as an upsell, as a faster lane or a catch-up. The method does not change. The room gets quieter.

A teenager in this room writes a short note a parent can read: what it does, what it will not do, what the log showed on Tuesday. Confidence scores are not decoration. If the camera calls a cup a shoe, they have to say so. That sentence is more valuable than a generated landing page they cannot edit.

A seven-year-old should leave with a game they can play. A sixteen-year-old should leave with a system they can pause and explain.

What does not change

Four students. One mentor. Understand, build, debug, show. Evening hours on Gulf time, because school already took the day. We will not “advance” a child by handing them a harder logo. We advance them when the artefact is honest at the next age.

If a school cannot tell you what the work looks like at each of those ages — in a sentence, with an artefact — they are selling the word code. We would rather show you the project. That is what the intro call is for: age, city, what they like to make. Then we match First Code, App Builders, or AI Engineers — or we say not yet.