Skip to content
Lesson 6

The Thinking Toolkit Capstone

This is the capstone for computational thinking. So far you have met four ideas. Decomposition, breaking a big thing into smaller things. Pattern recognition, noticing when two problems are the same problem in disguise.…

There is more than one way to understand this. If you have only been taught one, you have been taught less than you deserve.

There is more than one way to understand this. If you have only been taught one, you have been taught less than you deserve.

This is the capstone for computational thinking. So far you have met four ideas. Decomposition, breaking a big thing into smaller things. Pattern recognition, noticing when two problems are the same problem in disguise. Abstraction, dropping the details that do not matter so the shape becomes clear. Algorithms, writing the steps so anyone, including a machine, can follow them. Today you will use all four on one real problem from your own home.

Pick the problem first. Look around your house and find one small task that takes too long, gets done badly, or sparks fights. Filling and distributing drinking water bottles every morning. Sorting clean laundry into the right cupboards. Charging four phones with two chargers without anybody waking up to a dead phone. Putting the kachra out in the right colour bag on the right day. Pick one. Write it on top of a fresh page.

The Multan algorithm read like this. At nine pm, last person who washes hands fills the jug and puts it in the fridge. At ten pm, ammi pours into six labelled bottles already lined up on the second shelf. At seven am, whoever opens the fridge first hands out bottles to the names on them. By the third morning, the fights had stopped. Notice that the family did not buy a faster filter, did not get a bigger fridge, and did not yell at anyone. They just made the steps explicit and time stamped. The fight was never about water. It was about an unwritten algorithm that everyone interpreted differently.

Now do your version. Take your chosen problem. Decompose it into sub tasks until each sub task is one verb. Look at the list, do any sub tasks repeat across different problems you face. That is your pattern. For each sub task, ask what is the smallest set of facts I need to do this, and drop the rest. That is your abstraction. Then write the algorithm in numbered steps with names and times. Stick it where the people who do the task will see it.

Run the algorithm for one week. Watch where it breaks. The chai for guests sub task you forgot. The Friday when ammi is at the doctor and the eight o clock step has no owner. Each break is a debugging opportunity, not a failure. Update the algorithm. After two weeks of updates, your handwritten note will look more like a real piece of engineering than most things people call engineering. You will also notice the household runs smoother in ways you did not predict.

Today's habit. Pick the problem now, not later. Spend twenty minutes today writing the four pieces, decomposition, pattern, abstraction, algorithm. Stick the algorithm somewhere visible. Come back next Sunday with notes on what worked, what broke, and what you changed. Do this once and you have moved a household. Do this ten times across a year and you have built a way of seeing the world that very few people in any country actually have.

Estimated time: 14 min