World War II | Substitute Teacher
Students use simple coding concepts—sequencing, debugging, and pattern recognition—to complete a World War II history-themed activity appropriate for Grade 3. The lesson focuses on understanding how clear steps, events in order, and corrections are important in both coding and learning about history. Note: This is a history-themed coding lesson for young learners and does not include graphic or violent content.
| Term | Definition |
|---|---|
| algorithm | A set of steps in order to solve a problem or complete a task. |
| sequence | The order in which steps or events happen. |
| debug | To find and fix a mistake in a set of steps or code. |
| pattern | A repeated order or design. |
| event | Something that happens. |
Introduce the idea that coding is giving clear steps in the correct order. Model a simple non-digital algorithm, such as brushing teeth or making a sandwich, and connect it to history by explaining that events also happen in order.
Listen, answer questions, and help order the steps of the everyday example.
Present 4-6 age-appropriate WWII history event cards or pictures. Briefly explain each card in kid-friendly language. Ask students to help place them in a logical sequence. Keep facts simple and neutral.
Work as a whole class to discuss which event comes first, next, and last, then help arrange the cards in order.
Draw a simple flowchart or arrow sequence on the board. Show how each event card can be turned into a step in an algorithm. Model one mistake in the sequence and invite students to debug it.
Identify the wrong step, explain why it is out of order, and suggest the correction.
Give students a short set of 3-4 event slips or a worksheet. Ask them to number the events in order and write one sentence explaining the sequence. Circulate to support and check understanding.
Individually or with a partner, put events in order and write or say the steps as an algorithm.
Invite a few students to share their sequence and one debugged mistake. Reinforce that coding and history both depend on order and careful checking.
Share answers and reflect on how they solved the task.
Review that coding uses clear steps, and history often depends on events happening in order. Ask students to name one thing they learned about sequencing and one thing they learned about debugging.
Formative assessment through teacher observation, oral responses, and student sequencing worksheet or partner explanation. Students are successful if they correctly order most events and can identify at least one mistake in a sequence.