Active learning ideas
This final topic brings everything together as students write, test, and debug their own programs. They apply their knowledge of algorithms, variables, selection, and iteration to create a working piece of software. A major focus here is on 'debugging', the systematic process of finding and fixing errors.
Activity 01
Set up computers with simple programs that have one specific 'bug' (e.g., a missing variable or a wrong loop condition). Students rotate through the stations, identifying and fixing the bug at each one.
What is a bug?
Activity 02
After a coding session, students share the 'best' bug they found and how they fixed it. They brainstorm a 'Top 5 Debugging Tips' list to keep on their desks for future projects.
How do we systematically test a programme?
Activity 03
Students display their finished programs. Peers 'playtest' the software and leave constructive feedback on a 'Testing Log,' noting any bugs they found and what they enjoyed about the program.
Why is debugging a critical skill?
A few notes on teaching this unit
Watch Out for These Misconceptions
A 'bug' means you are bad at coding.
Even professional developers spend half their time debugging. Reframing bugs as 'puzzles to solve' through a 'Bug of the Week' celebration helps build a growth mindset and reduces frustration.
If the program runs, it is 'correct'.
A program might run but give the wrong answer (a logic error). Using 'test cases' with known inputs and outputs helps students see that 'working' means more than just 'not crashing'.
Methods used in this brief