You click "run" and… nothing. The screen freezes. The game crashes. Somewhere in the code, there's a bug — a mistake so small it might be one wrong letter, but powerful enough to stop the whole program cold. How does that happen?

Code is a list of instructions the computer follows exactly, step by step, like a recipe. "Add these two numbers." "Draw a circle here." "If the player presses space, make the character jump." The computer doesn't think or improvise — it just does what you wrote, in order, no questions asked.

A bug is when one of those instructions is wrong. Maybe you wrote "divide by zero" — which is mathematically impossible, like asking how many slices you get if you cut a pizza into zero pieces. The computer tries, can't, and crashes. Or maybe you told it to look for "player score" but accidentally typed "player scare" — so it searches for something that doesn't exist, gets confused, and stops.

Some bugs are logic errors — the instructions make sense individually, but the order is wrong. Imagine a program that's supposed to check if you have enough money, then let you buy a game. But the bug puts those steps backward: it lets you buy first, THEN checks your money. You end up with a negative balance and the program has no idea what to do.

Other bugs are infinite loops — when the program gets stuck repeating the same instruction forever. You meant to write "add one to the counter ten times," but you forgot to tell it when to stop. So it just keeps going: eleven, twelve, thirteen, a thousand, a million, forever. The computer is busy counting and can't do anything else. Your program freezes.

Tiny typos can be catastrophic. In one famous NASA mission, a missing hyphen in the code made a rocket veer off course and explode. In a game, forgetting one equals sign might make your character fall through the floor, or make enemies invincible. The computer doesn't see "close enough" — it sees exactly what you typed, and if that's wrong, the whole thing breaks.

Here's the tricky part: the program might work fine ninety-nine times, and break on the hundredth. That's because the bug only triggers under specific conditions — maybe when the player jumps at the exact moment an enemy appears, or when the number gets just high enough to overflow the space the computer set aside for it. You test the program, it seems perfect, and then a player finds the one weird thing you didn't try.

Finding bugs is detective work. Programmers read through the code line by line, add little checkpoints that print out "I got here!" to see where things go wrong, and test obsessively. When they find the bug — maybe it's one letter, one missing comma, one step out of order — they fix it, and suddenly the whole program comes back to life.

So a bug breaks a program the same way one wrong turn breaks a journey: the computer is trying to follow your map, but the map has a mistake, and now it's lost. Fix the map, and the journey continues. And that's why programmers say debugging is half the job — because even the best code is written by humans, and humans make typos, forget steps, and sometimes divide by zero.