"3, 2, 1, LET'S GO!" The project from last time already works — Eon resets it and replays it so any new kid watching can catch up: the cat jumps jump, jump, jump, jump across the stage. But it does it all in silence. The goal this time is to make the cat actually welcome people out loud — "Hello everyone, welcome to the channel!" To do that, Eon and his dad reach for Scratch's audio blocks.

Record your own voice with the mic

In Scratch you don't have to settle for the built-in beeps and meows. There's a little speaker for sound, and a mic you can tap to record your own. Eon wants that: "I want to custom myself!" His dad coaches him through the recording button, and it's trickier than it looks. The first tries fail because Eon is holding the button down. "Not just click and hold — you can just tap it once," his dad says. Tap once, the recording begins, and Eon speaks his line.

His dad even directs the performance: "You show more enthusiasm, right?" A flat, mumbled hello and a big cheerful one are the same blocks but a completely different feeling — so it's worth a second take just to sound friendly. That's a real lesson hiding inside a coding video: how something sounds is part of the design, not an afterthought.

Bug #1: why is there no audio?

Then comes the moment every programmer knows. They drop in the sound block, run it, and… nothing. "Why there's no audio?" Eon's dad doesn't panic — he narrates exactly what a developer does next: "Let me quickly test. Maybe we encounter some bug." Instead of guessing, he moves the cat to an easy spot to test it — "I'm going to move it here so we can quickly test" — runs it again, and this time the voice plays. "It works!"

Notice the strategy: when something is broken, you don't stare at it, you change one thing and test again until you learn what's wrong. That's debugging, and Eon just watched it done calmly instead of with frustration.

Sequencing: move to the center, THEN speak

Having the sound isn't enough — it has to play at the right moment. Eon re-records a clean take (his dad shows him that clicking the right button will override the old recording instead of adding a second one), and then they place it in order. Using just a finger, Eon drags the sound block along the sequence so the cat first travels all the way to the center, and then says its line. Move first, talk second. Get that order wrong and the cat would blurt its hello to an empty stage; get it right and the intro feels polished.

Now every single time the project resets, the cat walks to the middle and greets the audience on its own — "you don't need to" do anything, his dad laughs, "you just need to record it."

Bug #2: a little bit "buggy"

On a replay, the audio lags. "I think it should lag a little bit… it's a little bit buggy," Eon says — and his dad seizes the teaching moment:

"This is called a bug. Nothing is perfect — if you write a program, there will be a bug. Maybe Scratch itself has some bug. It doesn't really matter, as long as it works."

They re-record once more, it plays again, and that's the real takeaway of the whole episode: bugs are normal. Even a tool as big as Scratch has them. You don't have to be perfect — you test, you re-record, you keep going. The lesson ends with the best two words in coding: "High five — you made your first intro!"

Try it

Open any project and give your character one line to say. Tap the mic and record it — and like Eon's dad says, tap once, don't hold. Try a boring, flat version and then an excited version, and listen to the difference. Then drag the sound block so it plays after your character moves into place. If it doesn't play the first time, don't worry — that's just a bug. Move it, test it, re-record it, and keep going until it works.