demo · working version — draft content, pending editorial review
6–910–1213–15 half a day calm free digital native from the editorial team

Coding a little game together

Going from playing video games to making them: with colored blocks, a cat that moves when you tell it to. The moment the character obeys for the first time is pure magic.

¿lo probaron en casa? cuéntenlo

How it’s done

There's a huge border between consuming screens and creating them, and you cross it in one afternoon. With a free, visual block-based tool (something like Scratch), your son goes from playing to being the one who makes the game.

How to start knowing nothing:

  1. The first spell. Make the character move when you press a key. Nothing more. That instant —"it moved because I told it to!"— is the one that hooks them, and it doesn't require you to know how to code; you discover it by dragging blocks and trying things.
  2. It breaks and it gets fixed. The game will fail a thousand times: the cat walks through the wall, the score won't go up. That's not the exercise's error, it's the exercise. Hunting down why it doesn't work and trying something else is exactly what's being learned.
  3. A game with their stamp. Once something's moving, let them make it theirs: their drawings, their crazy rules, their sister as the villain. At the end, have someone else play it — the face of whoever tries your game is the prize.

What it builds — the why

Coding gives your son the lived experience of being on the inside of technology: understanding that behind every app and every game there are rules someone wrote, and that he can write them too. It builds logical thinking —breaking a problem into steps— and a rare, valuable tolerance for frustration: here, failing a thousand times is the path, not the failure. And it changes his relationship with the screen forever: it stops being just a place where he's given things and starts being a place where he makes things.

How it changes with age

6–9 Childhood
Very visual block-based tools, super short challenges: move a character, make a sound, paint the screen. The goal is the wonder of the machine obeying, not finishing a whole game.
10–12 Preteens
The golden age for this: they can already sustain a project across several sessions, invent levels, add scoring and enemies. If a friend joins in, even better — coding as a pair, arguing about what to do, multiplies the ideas.
13–15 Early adolescence
If the spark catches, give them the next step up: real text-based code, a more ambitious game, or even using AI as a copilot to understand an error. This is where something can be born that isn't a pastime but a calling.

Variations

Screen-free version (yes, it's possible): unplugged programming, giving an adult exact step-by-step orders to make a sandwich —and watching the disaster when the instruction is ambiguous—. Version with friends: a small challenge among several kids, each makes a mini-game and then they all play each other's.

What to watch for in your child

Watch which part grabs them: some are fascinated by the logic and the challenge of getting it to work; others by the drawing, the story, the level design. Both are coding and both count — don't push them toward the side that isn't theirs. If they get frustrated and want to quit at the first failure, help them find ONE bug, just one, and fix it: that small victory usually reignites everything. And if it turns out they're not interested, that's fine — not every child has to code, though every child gains from seeing it from the inside once.