Welcome to the Commands Series! In the last series — Programming for Kids: How Computers Think — you learned four big ideas that sit at the heart of every computer program ever written: Input → Process → Output — every device takes something in, works on it, and gives something back Sequence — instructions must happen in the right order Decisions — computers choose different paths depending on the situation Loops — computers repeat steps until a stopping rule is met That series answered the question: how does a computer think? Now there is a new question: how do you actually talk to one? You understand what computers do. But to make them do what you want , you need to give them instructions. Those instructions are called commands — and learning how to write them well is the real starting point of programming. What You Learned Last Time Idea What It Means ------ -------------- Input → Process → Output Computers take information, work on it, give a result Sequence Instructions must follow a specific order Decisions Computers choose different paths based on conditions Loops Computers repeat steps, stopping when a condition is met What You Will Learn in This Series Post The Big Idea ------ ------------- What is a Command? Every action starts with a command — you give it, the computer does exactly that one thing Commands Need a Receiver A command only works when something is there to receive and understand it Giving Good Commands Commands must be specific — computers cannot guess what you mean Putting It All Together How commands, sequence, decisions, and loops work together in every program You Are Already Giving Commands Every time you do any of these, you are sending a command to a computer: Press play on a music app → command: start playing Ask your phone "What time is it?" → command: tell me the current time Click a home button → command: go to the home screen Press pause in a video game → command: pause the game Tap the backspace key → command: delete one character to the left The computer is always waiting. The moment you give a command, it acts. This series is about understanding exactly how that works — and how to give commands that get the result you actually want. Questions People Ask What does "command" actually mean in programming? A command is one instruction telling a computer to do one particular thing — like a single button on a TV remote. Volume Up is a command. "Make the telly nicer" is not. Every program ever written is made of commands, so this is the smallest real building block there is. Do we need to read series 1 first? It helps, but it is not essential. Series 1, How Computers Think, explains what a computer does with an instruction once it arrives. This series explains how to give the instruction in the first place. If your child is keen to start here, they will manage fine. Is this the same as learning to code? Not yet — there is almost no code in it. What it teaches is the part that trips most beginners up: how to phrase an instruction so a machine can actually act on it. That skill is identical in Scratch, Python, JavaScript, or any language that has not been invented yet. My child talks to Alexa and Siri all day. Is there anything new here? Quite a lot. Using a voice assistant teaches you that it usually works. This series explains why it sometimes does not — whether the fault was your words, the device not listening, or the device not understanding — and that is exactly the thinking a programmer needs. What do we need, and how long does it take? Four posts, each a 5–10 minute read plus an activity of about ten minutes. You need paper, a pen, a few household objects and one willing volunteer. Nothing to install, nothing to sign up for, and no device required. A Note for Parents and Teachers This series teaches children how to give an instruction that a machine can actually carry out. It covers three things: what makes something a command rather than a wish, why a command needs a receiver that is switched on and able to understand it, and why "make the text bigger" fails where "set the title to 24 pixels" works. The best way to use it is out loud, together — one of you gives the commands, the other plays the machine. If you only do one activity, make it The Awkward Waiter in Giving Good Commands: a child orders food from a grown-up who must obey the exact words in the least helpful way those words allow. It is very funny, and the lesson about vague instructions lands in about four minutes. In a classroom, each post works as one lesson: read it, run the activity in pairs, then use the "Check Yourself" questions as the plenary. The Broken Receiver Game in Commands Need a Receiver scales up well to a whole class — hand out the fault cards and let groups diagnose each other. No devices, logins or licences needed. This is series 2 of 6 in the Kids Programming learning path. New here? Start from the beginning. ✅ Start with the first post: What is a Command? The TV Remote