Software does exactly what it's told. When it's told the wrong thing, even slightly, that's a bug.
A recipe says “1 tablespoon of baking powder”. Somebody typed “1 teaspoon”. You follow it exactly and the cake comes out flat. You did nothing wrong: the recipe did.
A bug is that typo in software. It’s a mistake in the instructions that makes a program do the wrong thing: show the wrong price, freeze, crash or lose your work.
Where bugs come from
- a small typing slip in the code
- a situation nobody thought of, like a name with an apostrophe
- two parts of an app that each work, but not together
- an update somewhere else that changed the rules
Why the name
Engineers called glitches “bugs” long before computers. A famous 1947 note records an actual moth found stuck in an early computer at Harvard: the “first actual case of bug being found”.
What it isn’t
It isn’t a virus. A bug is an honest mistake. Malware is written on purpose to cause harm.
Where the comparison breaks down
A recipe typo affects one cake. A software bug can affect millions of people at once, the moment the app updates.
How the words fit together
A bug often shows itself with an error message. Debugging is finding it. A patch fixes it.
When you report a bug, say what you did, what you expected and what actually happened. A screenshot helps more than you'd think.

When you'll hear it
“It's a known bug.” The team knows about the problem and it's on their list to fix.
“It's not a bug, it's a feature.” A joke: pretending a mistake was on purpose.
“Can you reproduce it?” Can you make it happen again on purpose, so someone can see it?
“How do customers report bugs to us? How do we tell them when one's fixed?”


