Bugs and debugging
A bug is a mistake in a program. Debugging is finding it and fixing it: predict, run, compare, fix, shown on a square that does not close.
Transcript
A bug is a mistake in a program. This program should draw a square, but the shape does not close.
Debugging means finding and fixing bugs. Use four steps: predict, run, compare, and fix.
First, predict what should happen: a closed square. Run the program and watch. Compare the result with your prediction. They are different, so there is a bug. Look closely: the turn is eighty degrees, not ninety.
Fix the block, and run it again. Now the square closes. Every programmer makes bugs, and finding them is a skill you can practise.
Remember: a bug is a mistake in a program, and debugging is finding and fixing it. Predict, run, compare, fix.
More in this series
1:278What is a program?
A program is a list of exact instructions the computer follows in order. Algorithm, sequence and bug, explained with a robot that makes a sandwich.
1:079Events: when something happens
An event is something that happens, like a click or a key press, and an event handler is the script that runs when it does. Shown with Scratch blocks.
0:5810Loops: repeat instead of copy
A loop repeats blocks so you do not copy and paste them. Repeat, forever, and drawing shapes with a loop, shown with Scratch blocks.
1:0811Variables: a named box for a value
A variable holds a value under a name, and the value can change. Score, set and change, and what score = score + 1 means.
1:0112Conditions: if and else
A condition is a true or false question. If runs blocks when it is true, else runs when it is false. A fork in the road, with an umbrella or a hat.
1:1013Functions: name a group of blocks
A function is a named group of blocks you define once and call many times. Define, call and parameter, with a draw-a-square function.
1:3815From Scratch to JavaScript
The same six ideas in blocks and in text: sequence, variable, condition, loop, function and event, plus what syntax and the console are.