There is a common assumption in tech education: teach the tools first, and the ideas will follow. Give a student Python, and they will find something to build with it. Enroll them in a web development course, and a product will emerge. After five years of working with young people across East Africa, we have found the opposite to be true.
The Problem With Starting With Syntax
When students learn to code before they have a reason to code, they learn to copy. They follow tutorials. They build the same to-do app, the same weather widget, the same calculator. These are fine exercises, but they do not build the instinct that matters most: the ability to look at the world and see something worth fixing.
We have seen students complete six-month coding bootcamps and still struggle to answer the question: what problem are you trying to solve? The tools are there. The motivation is not.
What Problem-Finding Actually Looks Like
In our Dreamer program, students spend their first weeks doing something that looks nothing like coding. They walk around their school, their neighbourhood, their home. They carry a notebook. They write down things that frustrate them, things that seem inefficient, things that people complain about but have accepted as normal.
"The best technology products in the world were not built by people who knew how to code. They were built by people who could not stop thinking about a problem."