What Code Actually Is

Lesson 1 · taught by Pip · free preview

Here is the plain idea: code is a list of instructions, written down, that a computer follows in order — one step, then the next, then the next. That's all a program is underneath. A recipe for a machine.

The computer is fast and tireless, but it is not clever. It does exactly what the instructions say, in exactly the order they're written. It won't guess what you meant. It won't skip ahead. It follows the list to the letter.

The recipe card

Think of a recipe card for baking bread. "Mix the flour and water. Add the yeast. Knead for ten minutes. Let it rise. Bake at 400 degrees." Each line is a small, clear instruction. A person follows them top to bottom and ends up with a loaf.

Code is that recipe card, written for a computer instead of a cook. Every line is a small instruction. The computer reads from the top, does the first thing, then moves to the second, and keeps going until the list runs out.

The difference is the computer's stubbornness. A cook who reads "add salt" knows roughly how much. A computer needs to be told exactly — a pinch means nothing to it. If you forget a step, it won't fill the gap with common sense. It just does what's there. 🔦

Why this is good news

That literalness sounds like a headache, but it's a gift. Because the computer only does what you wrote, when something goes wrong the cause is in your instructions — a step missing, or two steps in the wrong order. The machine isn't moody. It's faithful. That means a problem is always something you can find and fix.

So the "hard" part of programming isn't the typing. It's thinking carefully: breaking a goal into small steps, putting them in the right order, and leaving nothing to chance. If you can write out clear directions to your house — turn here, go straight, stop there — you already have the core skill.

Languages are just dialects

You may have heard names like Python, JavaScript, or Java and felt a little dizzy. Don't. Those are programming languages — different ways of writing the same kinds of instructions, the way English and Spanish are different ways of giving the same directions.

One language might write "show the word hi" as print("hi") and another as console.log("hi"). Different spelling, same instruction. Underneath, every language shares the same handful of building blocks — boxes for values, yes-or-no questions, repeating, bundling steps, keeping lists. Learn the ideas once, and any language becomes a matter of looking up the local spelling.

Your turn

No computer needed. On paper, write the exact steps to make a peanut butter sandwich — for someone who takes every word literally and has never seen one.

Now read it back as that stubborn helper. Did you say to open the jar before scooping? Did you say which side of the bread? Every gap you spot is exactly what a computer would catch. Finding those gaps is the real skill — and you just did your first round of it. 🐙

Next up: variables — the labeled boxes where a program keeps the things it needs to remember.