Why Every Hong Kong Child Should Learn to Code (Even If They Won't Be a Programmer)

The question I hear most from parents at school open days isn't "will my child enjoy coding?" It's "do they actually need it if they're not going into IT?" The honest answer requires me to explain something that gets lost in the headlines about coding bootcamps and tech salaries.

Coding is not primarily about getting a tech job. Coding is about learning to think in a way that has become essential to understanding the modern world — and Hong Kong's place in it.

What coding actually teaches

When a student learns to write a programme, they encounter a set of challenges that don't exist anywhere else in the curriculum. They have to decompose a problem — break something large and vague into steps that are small and precise. They have to anticipate failure — every programme fails before it works, and that failure is information, not defeat. They have to think sequentially and conditionally — if this happens, then that; otherwise, something else. They have to debug — find the one thing that's wrong among many things that are right.

These cognitive skills transfer. I've watched students who struggled with long essay planning suddenly grasp it after a term of coding, because they'd learned to outline a process step by step. I've watched students who gave up at the first maths mistake become more persistent after they accepted that programmes always have bugs and bugs are findable.

The Hong Kong context matters

We live in a city where financial services, logistics, and professional services are being reshaped by automation at a pace that is faster than elsewhere. The EDB has recognised this: the 2021 STEM strategy and subsequent AI literacy initiatives are responses to a real economic pressure. When your child reaches the workforce in 10-15 years, they will almost certainly work with automated systems. Whether they understand how those systems work — at even a basic level — will affect every aspect of their professional life.

I'm not predicting that your child needs to become a software engineer. I am saying that a child who has never understood how an algorithm works, how a decision tree is structured, how data is stored and retrieved, will be at a disadvantage in roles from banking to healthcare to law.

Consider something as simple as this: a student who has done basic coding understands what a conditional statement is. When they grow up and a bank's system automatically declines their loan application or flags their account, they know that a rule in a system made that decision — and they know there may be a way to challenge or understand it. A student who has never encountered this concept simply accepts the machine's decision as if it came from nowhere.

Starting early: what the evidence says

Primary school is the right time to begin. Not because young children need to learn syntax — they don't — but because the habits of computational thinking form most naturally before the academic pressure of secondary school starts crowding everything else out.

The EDB has been introducing coding activities into the primary curriculum, and there are good reasons for this timing. At P3-P5, children are naturally creative problem-solvers who haven't yet learned to be afraid of being wrong. That psychological window is precious. Block-based coding tools like Scratch let students experiment without the barrier of syntax, focusing entirely on the logic.

By the time they reach secondary and encounter text-based programming, the logic is already familiar. They're just learning a new language for thoughts they already know how to think.

What I'd actually recommend by age

For P1-P3: Don't start with a screen. Unplugged coding activities — flowcharts, sorting games, instruction-writing exercises — build the thinking without the distraction. The goal is to understand that computers follow instructions literally, and instructions need to be exact.

For P4-P6: Scratch (scratch.mit.edu) is the standard starting point, and it remains excellent. An hour a week, exploring freely and building small projects, is worth more than a structured class that moves faster than children are ready for.

For S1-S3: Python is the language I'd recommend for this age, not because it's the "best" language in any absolute sense, but because it's readable, the error messages are human-like, and it's what university computing courses almost universally use as an introduction.

For S4 and beyond: This is where individual interest should guide the path. Web development, app development, data science, game development — each teaches different things and suits different students. The ICT elective is one option; self-directed learning with structured online courses (freeCodeCamp, CS50) is another.

Addressing the main objection

"My child isn't good at maths — can they still learn to code?" Yes. The overlap between maths and coding is real but often overstated. Primary-level coding requires arithmetic and basic logic, not algebra. Secondary coding introduces more mathematical thinking, but plenty of excellent programmers are mediocre at formal maths. The skills are related but not identical.

"They have too much homework already." This is the hardest objection, because it's real. Hong Kong's academic pressure is not imaginary. But I'd gently push back: an hour a week on Scratch for a P5 student is an hour of genuine skill development that compounds over years. The question is whether that hour is more valuable than one more round of practise questions. In my experience, for most children, the coding hour builds more transferable capability.

The question nobody asks

I'll close with the question parents rarely ask but probably should: what happens if your child grows up to be a doctor, a lawyer, a teacher, an accountant — and they don't understand how the AI tools making decisions in those fields actually work?

Not understanding the technology that shapes your professional world isn't neutral. It makes you dependent on those who do understand it. Coding, at a basic level, is the beginning of not being dependent.