Glitch

Loop was trying to make her game character, Pip — a little pixelated frog — jump. She typed the code, pressed Run, and instead of leaping high, Pip just wiggled sadly on the ground. Loop sighed. "Oh, Pip. What did I do wrong?"

A tiny glow appeared, hovering gently over one line of code. Glitch. No red flash, no loud noise — just warm and curious. Loop's shoulders came down, and she smiled a little. "Thanks, Glitch. I forgot. There's always a reason." She looked at the screen, where a small message read: TypeError: cannot multiply sequence by non-int of type 'float'. "See — Glitch reminds us to read the error message. These are helpful hints — they tell you where the problem is and what kind it is. 'TypeError' means I used the wrong kind of data." She scrolled to the line Glitch hovered over: jump_power = "5" jump_strength. "Aha! I put quotes around the five — that makes it text, not a number. You can't multiply text like that." She fixed it: jump_power = 5 jump_strength.

She ran it again. Pip still wiggled — but the error was gone. "Okay, new problem — no error message this time. So what's next, Glitch?" The warm light pulsed. "Right! Print debugging. You make the computer tell you what's happening inside — like asking the code, hey, what number are you holding right now?" Loop added print(jump_power) and print(jump_strength), ran it, and watched the console:

50 10.0

"Hmm. Jump power is 50, jump strength is 10 — that seems fine. But Pip still isn't jumping. So the trouble's somewhere later." She wasn't frustrated. She was curious now — the bug was just a clue she hadn't followed yet.

"Another trick is stepping through with a debugger," Loop told Glitch, "like pressing pause on a video game — you stop the code and watch every value, moving forward one tiny step at a time." She set a breakpoint and ran it, and the program froze mid-jump so she could see every variable. "Good for tricky bugs. But sometimes you just need to talk it out." She reached for a small green rubber duck. "Okay, Mr. Quackers. Pip the frog isn't jumping. My code sets jump_power, then updates Pip's position, then—" She stopped dead. "Wait a minute. I set Pip's y position to 0 after I add the jump power — so he lands back on the ground immediately!" She'd found it — that was rubber-duck debugging, where explaining code out loud lets your own brain hear the mistake. She swapped the two lines, put the position update before the jump, and ran it. Pip leaped — a perfect pixelated flip. "YES! Good job, Pip! Good job, Mr. Quackers!" Glitch's light pulsed happily.