Kavi, the KAVI owl, waving on a book
HomeAcademyAIWho it's forPricingFAQLabsContactGet Started
AI Literacy · Stage 5

Debug Across Tries

Build it, test it, find the bug, then change ONE thing and try again — until it works.

✦ AI Literacy📘 Stage 5 · S5⏱ ~9 min🧒 Ages 9–10★ Free to start
I can test, find a bug, and fix it.
Start the free lesson →⬇ Printable PDF
Kavi the owl for AI Literacy
📖

Kavi's Three Claps

Kavi the owl built a little robot to clap 3 times. She tested it — Try 1: clap! Just one clap. "Hmm, not three," said Kavi. She didn't start over. She found the bug — the code said repeat 1 — and changed just that one thing to repeat 3. She tested again — Try 2: clap, clap, clap! "Test, find the bug, fix one thing, try again," hooted Kavi. "Every try gets me closer!"

🎓

What your child will learn

1Test → Find → Fix → Try againMakers don't build once and hope. They go round this loop, one try after another, until it works. Tap each step!
2Change ONE thing vs change lotsWhen a try fails, how much should you change before the next try? Tap each side!
3What's the smart move?Read each one and pick the move that gets you closer across tries. Pick, then tap to check. Tap Next for more!
🔍

A peek inside

You built a counter that should count 1, 2, 3, but Try 1 prints 2, 4, 6. How do you debug it?
First I TEST — I ran it and it printed 2, 4, 6, not 1, 2, 3. That's not what I meant. I FIND the bug: it jumps by 2 each time, so the step says 'add 2'. I FIX just that one thing — change 'add 2' to 'add 1'. Then Try 2: it prints 1, 2, 3. Fixed!

Try this at home: Right after you fix a bug, what should you do?

💬

Questions parents ask

+What does it mean to debug across tries?

It means you don't expect your build to work the first time. You test it, find the bug, change one thing, then test again — that's a new try. Each try gets you closer, and you keep going round the loop until the build does what you meant.

+Why change just one thing between tries?

So you can tell exactly what fixed the bug. If you change five things at once and the next try works, you still don't know which change helped. Change one thing, test, and every try teaches you something real.

+How does comparing two tries help you find a bug?

When you change one step and run the next try, the difference between what Try 1 did and what Try 2 did points you to the bug. Comparing tries is how you narrow down where the problem is.

+If my first tries fail, should I give up?

No. A bug you have found is a bug you can fix. Failing tries are not the end — they show you more about where the problem is. Good builders keep testing and fixing, one small change at a time.

+What age is this 'Debug Across Tries' lesson for?

It is a Stage 5 lesson for roughly ages 10–11 in KAVI Academy's AI-literacy and creating-with-AI track. It uses ordering, sorting and find-the-bug puzzles with light reading.

+Is the lesson free?

Yes — this overview and the printable PDF handout are free. The full interactive lesson and the endless practice are part of KAVI Academy.

Ready to play and learn?

Start the free interactive lesson, or print the handout for screen-free play.

Start the free lesson →⬇ Download PDF

Part of AI Literacy · Stage 5 · S5 on KAVI Academy — a secular, whole-child learning platform for ages 5–12.