Programming a Human Robot

Overview

The single most important thing a child can understand about programming is that computers are literal. They do exactly what you tell them — no more, no less. They don't fill in gaps, they don't assume context, and they don't know what you meant to say. This activity makes that painfully, hilariously clear by turning a parent into a robot who can only follow exact instructions.

Setup

The Obstacle Course (5 minutes):

Set up a simple path in a room or hallway. A chair to walk around, a pillow on the floor to step over, a toy at the end to pick up. Nothing complicated — three obstacles is plenty.

Make sure there's enough space to walk safely. Clear anything breakable from the path.

The Sandwich Station (optional, for Part 2):

Set out bread, a spread (peanut butter, jam, hummus — whatever your child eats), a plate, and a butter knife. Leave everything closed and in its packaging.

Instructions

Part 1: The Robot Walk (15 minutes)

Announce: "I am now a robot. I can only do EXACTLY what you tell me. I don't think for myself. I don't guess. I only follow your instructions."

Stand at the starting line of the obstacle course. Your child is the programmer. Their job: get you to the end of the course and pick up the toy.

The key: Follow every instruction LITERALLY.

If they say "Walk forward," start walking forward and don't stop (they didn't say when to stop). If they say "Go to the chair," stand there confused — you don't know what "go" means (do you crawl? slide? hop?). If they say "Walk around the chair," walk in circles around it indefinitely (they didn't say how many times or when to stop).

Be playful, not frustrating. When you "malfunction," freeze and say in a robot voice: "ERROR. Instruction unclear. Please reprogram."

Your child will quickly learn to be specific:

• Not "walk forward" but "take three steps forward"
• Not "go around" but "turn right, take two steps, turn right, take two steps"
• Not "pick it up" but "bend down, grab the teddy bear with your right hand, stand back up"

After the first run, ask: "What did you learn? Why did the robot keep making mistakes?"

The answer you're guiding them toward: "Because I wasn't specific enough."

Run it again. Watch their instructions sharpen dramatically.

Part 2: The Sandwich Challenge (15 minutes)

This is the classic programmer exercise, and it's magic every time.

"The robot is hungry. Program the robot to make a peanut butter sandwich."

Follow every instruction literally. The results are always funny:

• "Put peanut butter on the bread" → slam the closed jar onto the bag of bread
• "Open the peanut butter" → they didn't say "unscrew the lid," so try pulling, pushing, biting
• "Spread the peanut butter" → smear it with your hand (they didn't say to use the knife)
• "Use the knife" → pick up the knife and hold it, doing nothing (they didn't say what to do with it)

Your child will be laughing and refining. By the third or fourth attempt, they'll be producing precise multi-step instructions: "Pick up the knife with your right hand. Scoop peanut butter from the jar with the knife. Spread the peanut butter on one side of one piece of bread."

Eat the sandwich together when you're done. The programmer earned it.

Part 3: Role Swap (5 minutes)

Now your child is the robot. You give the instructions. Start with simple ones and sneak in a deliberate error: "Take three steps forward. Turn left. Take one step forward." (When a left turn would make them face a wall.)

Let them experience being the robot — following instructions they know are wrong but executing them anyway because that's what the code said.

Ask: "How does it feel to be the robot? Did you want to say 'that's wrong' but you couldn't because robots just follow instructions?"

What to Watch For

• Precision growth: Compare their first attempt at instructions to their last. The leap in specificity is the learning.
• Frustration vs. curiosity: If they get frustrated when the "robot" misinterprets, remind them: "That's what real programmers deal with every day. The computer never understands what you MEANT — only what you SAID."
• Debugging instinct: Do they figure out which specific instruction caused the problem? That's debugging.
• Decomposition: Can they break "make a sandwich" into 10+ individual steps? That's computational decomposition — a core computer science skill.
• Empathy for machines: Do they start to understand why computers sometimes "do the wrong thing"? It's almost always because the instructions were incomplete.

Variations

• Drawing Robot: One person gives verbal instructions to draw something (a house, a face) without the drawer seeing the original. "Draw a circle in the middle of the paper. Draw two small circles inside the top half of the big circle." The gap between what was intended and what was drawn is the gap between intention and code.

• Maze Robot: Draw a simple grid maze on paper. One person gives directions (up, down, left, right + number of squares) to navigate through it. This introduces the concept of coordinates and movement commands.

• Multi-Robot: If siblings or friends are present, have two "robots" receive the same instructions but interpret them differently. This demonstrates why code must be unambiguous — different processors shouldn't produce different results.

• Written Programs: For ages 7-8, write the instructions on index cards before executing them. Then "run the program" by flipping cards one at a time. This separates writing code from running code — a real distinction in programming.

Reflection Prompts

After the activity — at dinner, in the car, or before bed:

• "What was the hardest part about programming the robot?"
• "Why do you think real programmers have to be so specific?"
• "If you could program a real robot to do one thing in our house, what would it be? What instructions would you give?"
• "Have you ever followed instructions that didn't quite work? What happened?" (Think LEGO manuals, recipes, game rules.)