Break Problems Apart
Big tasks feel impossible until you split them into small steps. Each step should be clear enough to do or check.
- Split a school task into ordered subtasks
- Write steps small enough to follow without guessing
- Spot when a step is still too vague
Topic contents
Lesson 1 of 3
One big job, many small jobs
Organising a class event looks huge: room, posters, snacks, music. If you write one step that says make the party happen, nobody knows where to start.
Split the job. Step one might be book the hall. Step two design a poster. Each piece is small enough that one person could finish it in an hour.
Programs work the same way. Software is not one magic button. It is hundreds of tiny instructions grouped into parts that each do one job well.
Lesson 2 of 3
Checkable steps
A good subtask has a finish line you can see. Bad: make it nice. Good: hang twelve posters on floors one and two by Friday.
If you cannot tell when a step is done, break it again. Nice is a feeling. Twelve posters is a count.
When coding later, functions will mirror these subtasks. One function draws the score. Another moves the player. Same idea, different tool.
Lesson 3 of 3
Order still matters
Subtasks depend on each other. You cannot frost a cake before you bake it. List steps so prerequisites come first.
Draw a simple list or sketch arrows between boxes. You do not need fancy software. Paper works.
Next you will trace programs on paper, watching variables change one line at a time.
Practice
Work these out yourself
No answer key here on purpose: these are the questions worth thinking through before you move on. Open one and work it out.
0/3 attemptedAssessment
Check your understanding
Answer each question, then read the explanation. That is where the learning is.
Finished this topic?
0 of 3 lessons marked done. Marking the topic complete ticks the rest.