Before you build a single game, you need one idea in your head: what is coding, really? In Coding Lab 3, Eon and his dad don't open an app or type a line of code. They just look around the room — at the camera, the microphone, the iPad — and ask a simple question about each one. By the end, Eon can say the answer himself in a single word.

Machines don't move on their own

Eon's dad starts with something Eon already half-knows: almost everything we use today runs on electricity, and that makes it a kind of machine. But here's the catch he wants Eon to really feel — machines "do not move on their own." They only ever do things by "following certain instructions." We tell the machine to do this, then do that.

To prove it, he points around the room at the gear that's recording the lesson:

  • The camera is recording them right now. Why? Because someone pressed the record button. Press once to start, press again to stop. No press, no recording.
  • The mic has a little volume indicator. Talk quietly and it stays calm. But — as Eon's dad warns — say something really loud and it shoots "all the way to the danger zone" and the sound "pops." The mic isn't deciding to do that; it was built with an instruction: if the volume is too high, show red.

Every machine is "following certain order." Click this button, start recording. Click again, stop recording. That's the whole secret.

The sneaky camera lesson: don't just trust the AI

Then comes the smartest moment in the video. Eon's camera isn't an ordinary camera — it's "AI embedded." It can actually track your eyes and move on its own to follow whoever's talking. So why is it sitting still? Because Eon's dad told it to stop following. Otherwise, he explains, it would swing over to Eon and then back to record him — chasing faces around the room.

And he uses that to drop a line worth remembering for life:

"Sometimes AI can make mistakes. That's the reason we have to understand things."

The point isn't that AI is bad. It's that because it can get things wrong, we learn how things work — so we can give the machine better instructions and make it actually help us, instead of blindly trusting it. For a kid growing up surrounded by AI, that's a powerful habit: be the one who understands, not just the one who taps and hopes.

How a game actually works

Now the idea lands where Eon cares most — games. Inside a machine, Eon's dad explains, there are lots of different apps and different games, and code is how you tell each one what to do. That means you can design a whole game or a whole app.

Here's the part that clicks: when other people open your app and play your game, every time they tap the screen, they "receive that instruction" you wrote. The game's logic is just a chain of if this, then that:

  • They clicked? Show something.
  • Play an animation.
  • Play some music.

"That's basically how a game works. That's basically how programming works." A game isn't magic — it's a pile of instructions, sitting quietly, waiting for a tap.

To check it stuck, Eon's dad runs a quick call-and-response: "We programmers, we write — what?" And Eon fills in the blank himself: "Instructions." So the machines know what to do, and follow them. That's the whole lesson in one word.

Try it

Be the programmer for a real machine: a toaster. Write its "code" as numbered steps, in order:

  1. Get a slice of bread.
  2. Put it in the toaster.
  3. Push the lever down.
  4. Wait until it pops up.
  5. Take the toast out.

Now play "very literal robot." Have someone follow your steps exactly — but this time delete step 3 (push the lever) and read it again. The robot drops bread in and just... stands there. Cold bread, no toast.

That's the big idea from Eon's lesson: machines only do what you tell them, in the order you tell them. Write clear, complete, in-order instructions — and you're coding.