The Human Robot

Computers do exactly what we tell them to do — no more, no less. Before your child learns to type code into a screen, they must learn how to give and follow step-by-step instructions. In this module, you become the robot, and your child becomes the programmer.

Kindergarten · Ages 4–6 Project Duration: 30 minutes No electricity required

Works offline · No login · Yours to keep

⚠ A Note for Grown-Ups This is a physical game of logic. Young children often think computers are "smart." The goal here is to show them a computer is actually quite "silly" — it has no brain of its own and only does exactly what its programmer tells it to do. When you play the Robot in the living room, be extremely literal, and keep any obstacle soft — a pillow, never a hard table corner. The first bug should feel like a fun discovery, not a failure: react with delight, not an error buzzer.

TRY IT FIRST

Algorithm Simulator

T · Technology · E · Engineering

Before you play the physical game, try writing code here. Click the command blocks to build an algorithm that moves the Robot (triangle) to the Goal (star) without hitting the soft obstacle (pillow square).

⟁ Write Your Code

Add blocks to the sequence, then click RUN.

No commands yet. Click buttons above.

Awaiting instructions.

Try This A straight line of four Forward blocks will run right into the pillow — that's the bug to discover first. A working program goes around: try Right, Forward, Left, Forward times four, Left, Forward to trace a path above the obstacle and land right on the goal.

The Full Module — Reading Mode

⚠ On Being Literal & Safety Young children often think computers are "smart" because they play videos and games. The goal here is to show them a computer is actually quite "silly" — it has no brain of its own and only does exactly what its programmer tells it to do. When you play the Robot, be extremely literal. "Walking into the obstacle" should never mean an actual collision — use a soft pillow, never a hard table corner. When the Robot reaches the obstacle, slow to a stop and freeze with exaggerated comic surprise ("BZZZT!") rather than physically bumping into it. The first bug should feel like a fun discovery, not a failure — your tone teaches your child how to feel about mistakes.

What This Is

An algorithm is just a recipe — a set of instructions given in a specific order to get a job done. If you want to bake a cake, you can't put the flour in the oven before mixing it with eggs. The order matters. Computer code works the exact same way: a recipe for a computer to follow.

In this activity, your child draws "code blocks" (arrows on paper), arranges them on the floor to build an algorithm, and you — the Human Robot — read their algorithm and execute it perfectly to navigate an obstacle course.

This isn't a loose metaphor. Real Mars rovers are controlled with command sequences built from exactly this small set of moves: turn left in place, turn right in place, and move forward — the same three actions your child will be giving you today. The order those commands arrive in determines everything the rover does, with no room for "it probably meant."

The Code Blocks

The programmer writes their code by drawing four types of Code Blocks on separate pieces of paper (at least 5 of each):

[ ↑ ] = Take one step FORWARD
[ ↓ ] = Take one step BACKWARD
[ ↰ ] = Turn your body LEFT (no step, just spin in place)
[ ↱ ] = Turn your body RIGHT

Left/Right Tip Telling left from right is genuinely hard at this age — most children don't reliably master it until 6 or 7, and that's completely normal. If your child mixes them up, try marking one of their hands with a sticker, or simplify to landmarks ("spin to face the couch," "spin to face the window"). The algorithm-building lesson works exactly the same either way.

Notice and Wonder

After the robot successfully reaches the goal, sit down and talk about what happened. Did the robot know where to go on its own? No — it needed the arrows. What happened when the arrows were in the wrong order? The robot stopped at the obstacle. If we move the obstacle to a new spot, does the old code still work, or do we need to write new code?

Code is communication — a way to talk to a machine using very simple, specific steps. By physically moving paper arrows to change your behavior, your child is practicing the exact same kind of command sequence that controls real rovers exploring Mars: move forward, turn left, turn right, in a precise order, with zero room for guessing.

Field Engineering: Step by Step

STEP 1

Set the Course. Place a Start marker (a pillow) on one side of the room. Place a Goal marker (a stuffed animal) on the other side. Put a soft obstacle — another pillow or stuffed animal, never hard furniture — somewhere in the middle of the path.

STEP 2

Write the Code. The child looks at the course and lays their paper Code Blocks down in a line on the floor, like a train, to tell the Robot how to get from Start to Goal.

STEP 3

Power On. You stand on the Start marker. Beep and boop a little to confirm you're ready to receive data.

STEP 4

Execute the Algorithm. The child touches the first paper arrow. You execute that one step exactly. They touch the next arrow. You execute that step. No guessing what they "meant."

STEP 5

The Bug — a Fun Discovery. If the code sends you toward the obstacle, slow to a gentle stop right at it — never collide — and freeze with delighted, exaggerated surprise: "Ah ha! Object detected! BZZZT! I cannot continue!" Treat it as a fun discovery, not a failure.

STEP 6

Debugging. Explain that the robot isn't broken — the algorithm has a bug. Have the child swap the wrong paper arrow for the correct one, then restart the program from the very beginning.

The Human Robot

Algorithm Simulator

⟁ Write Your Code

The Full Module — Reading Mode

What This Is

The Code Blocks

Notice and Wonder

Field Engineering: Step by Step

Build It For Real

Materials

Complete Project Checklist

Getting Ready

Building the Algorithm

Testing and Debugging