Systems Connect Everything

I just finished teaching the whole System Design lesson at A/L, how a system works, what we can actually do with one, and how the whole thing fits together. And the same feeling came back to me. Students still try to memorize the definitions, and they never reach the idea behind the systems.

Most teaching outside tuition stops at the surface. This is a system, here is the list of systems, here is the definition, and that is it. Nobody tells the real stories behind systems, how they came to be, or how one connects to another. That is the part that actually makes it click.

Here is the thing people miss. System design is not just a lesson. It is the thread that ties together every one of the 13 lessons in the syllabus. Once you see that, the subject stops being a pile of separate topics and turns into one connected picture.

Pick a student from almost any school and they can tell you what a system is and what a system can do. But ask them what a system actually is. Ask whether software is a system, or a system is software, and they go quiet. That is the real gap. There is no foundation, no behavioural or overall understanding sitting under the words.

And that gap follows them. More and more students chase only the papers, and that is fine, because we do have to sit the paper. But overall understanding is the easier path. It keeps you current with ICT, and honestly it earns a better score too, not a worse one.

I am fairly sure the coming papers will test understanding, not definitions. Back in the day the paper checked definitions, and teachers drilled students on exactly that tactic. That style is not going to work much longer.