Coding for Kids, Stage by Stage from Age 5 to 15

The first step in coding for kids happens on the floor at home. In the human robot game, the child calls out commands such as "forward three steps, turn right, forward two steps" to a helper who plays the robot and carries them out exactly as spoken. When the robot walks into a chair because a step was skipped, the child sees for themselves that a machine does only what it is told, in the order it is told. That moment plants the idea of a sequence, a clear order of steps, in children aged 4 to 7 who do not yet need to read.

Paper arrow cards take the game further. The child lays out a row of cards to guide a toy from one floor tile to another, runs the route, and checks whether the toy arrives. A later version adds a "repeat twice" card, which is a first taste of loops. Screen-free robot toys offer another way to practise the same thing: Cubetto is designed for ages 3 and up, and Bee-Bot, a small bee-shaped robot, can store up to 40 direction commands. Homemade cards build the same skills for almost no cost.

All of these games train the four pillars of computational thinking: decomposition, or breaking a big job into parts; pattern recognition; abstraction, or keeping only the information that matters; and algorithms. A child who retells the steps of brushing their teeth, then repairs a version that has been deliberately shuffled, is writing an algorithm without knowing it. The sign that this stage has settled is easy to spot: the child can build a five or six step route alone, and when it goes wrong they can point to the card that needs changing.

Scratch opens in a browser on an ordinary laptop with nothing to install, and its community has passed 100 million registered users worldwide. This visual language from the MIT Media Lab labels its blocks with words, so it suits children who already read short sentences with ease, usually from about 7 or 8. The first two terms a child learns here are sprite, meaning any character or object that can be given commands, and stage, the backdrop where every sprite appears.

The Scratch stage measures 480 by 360 points. The x coordinate runs from minus 240 on the left to 240 on the right, and y runs from minus 180 at the bottom to 180 at the top, with zero in the exact centre. Understanding this grid lets a child place a sprite precisely and move it with a "change x by 10" block. A good drill is to put three sprites in three corners of the stage by typing coordinates alone, then guess where each will appear before pressing the green flag.

Event blocks open every script: "when green flag clicked", "when space key pressed" or "when this sprite clicked". For animation, the child switches between a sprite's costumes with a short wait in between, so the character appears to walk. For a story with several scenes, the broadcast block lets one sprite signal to another when it is their turn. A child who can build a three-scene story with clean background changes has a solid grip on how events flow in Scratch.

Programs that misbehave are a normal part of coding, and the way a child handles them shapes whether they keep going. The cycle of trying, spotting the mistake, fixing it and trying again is called debugging. At the block stage the usual bugs are easy to recognise once you know them: a sprite that never moves because its script has no event block on top, a score that jumps by two because two scripts add to it at the same moment, a sprite that vanishes because its coordinates left the stage, or movement too fast to see because there is no wait.

A method children can learn early has four steps. First, make the problem happen again so it is clear exactly when it appears. Second, read the script aloud block by block, as if you were the computer running it. Third, change one thing only, then run it again. Fourth, if the cause is still hidden, pull out the suspect script and test it on its own. Many children find the bug while explaining their script to someone else, or even to a toy sitting on the desk.

The emotional side deserves equal attention. Young children often read an error as proof they have failed, when adult programmers spend a large share of their day hunting bugs too. A helper does most good by keeping their hands off the mouse and asking guiding questions: "What did you expect to happen? What actually happened?" The skill is taking root when a child can describe a bug in their own words, name a likely cause and try a fix before asking for help.

Young teenagers who have crossed the text bridge are ready for Python in full. The material moves from variables and user input, to if, elif and else branches, then to lists for holding many values and functions defined with def for steps that get reused. A good first project is a text game such as guess the number: the computer picks a random number, the player guesses, and the program says too high or too low until the guess is right. In a dozen or so lines it brings together a while loop, conditions, variables and the random module.

The second track is the web. HTML holds the content of a page, CSS controls how it looks, and JavaScript makes it respond to clicks. Many teens start with a personal profile page listing their hobbies and projects, then add a button that changes the background colour. Students who like physical things can try a micro:bit with MakeCode or a basic Arduino, where code switches on lights and reads sensors. An introduction to AI for teenagers also starts to make sense at this age, for example training a simple model to recognise images.

The habit that sets this stage apart is planning before typing. The student writes the steps of the program in plain sentences or a flowchart, divides them into functions, and only then starts coding. Those drawn to competitions can try Bebras Challenge tasks, which test computational thinking, and later the OSN Informatika track, Indonesia's national informatics olympiad, which goes deeper into algorithms. The skill is in place when a teen can split a project into functions, give variables clear names and read code someone else wrote.

Plenty of children arrive at coding through games they already love. Common Sense Media found that only about 3 percent of teenagers' screen time goes to creating, such as writing, coding or digital art, with the rest spent watching and playing. Coding offers a way to shift that balance while keeping the child inside the world they enjoy: Roblox fans build their own experiences in Roblox Studio, Minecraft fans use Code Builder in Minecraft Education to have an agent build walls for them, and children who love animated videos make their own animations in Scratch.

Time limits still matter, especially for young children. The WHO recommends no screen time for babies under 1 and at most 1 hour a day for ages 2 to 4. For children over 2, the expert guidance cited by IDAI, the Indonesian Paediatric Society, sits at around 2 hours a day. For school-age children, the American Academy of Pediatrics uses its 5 Cs framework (Child, Content, Calm, Crowding Out, Communication), which looks at what the screen time contains and how it fits around sleep and active play. That is one reason early coding for young children leans heavily on screen-free play.

A practical way to begin the shift is to log the child's screen activity for a week in three groups: watching, playing and creating. The device's screen time report supplies the totals. The child looks at the results too, then helps agree on a small but definite share for creating, such as two game-building sessions a week. Screen-free tasks such as designing game levels on paper can sit in between. At the end of each month, the share of creating time is compared with that first week's log.