A teacher writes 23 on the board and explains that it equals 8. One child in the class stares at it. 2 times 3 is 6, so why is the answer 8?
The explanation is that 23 means 2 × 2 × 2. That only helps a child who is already comfortable with what multiplication is. If multiplication is still a set of memorised facts, or still shaky, the explanation slides straight past them. The class moves on. Next week it's the laws of indices. The child looks around, sees everyone else nodding, and comes to a quiet conclusion: "I'm slower than the others."
That conclusion is usually wrong, and it does more damage than the missing maths ever did.
Quick Answer: Most kids who fall behind aren't slow. They're missing a concept that the next concept depends on. Learning is cumulative: you can't understand powers without multiplication, or multiplication without addition. When a class moves on before a concept is secure, the gap grows with every new topic, and the child often blames their own ability, which hurts their self-esteem. At DotCode Campus, in every course, we teach concepts upon concepts. We cover the underlying ideas thoroughly, check that each student really understands them, and only then build the next idea on top.
Every Concept Stands on Simpler Ones
Follow the powers example down and you can see the whole structure:
- Addition: 3 + 3 + 3 + 3.
- Multiplication is repeated addition: 3 × 4 is a shorter way to write that same sum.
- Powers are repeated multiplication: 34 means 3 × 3 × 3 × 3.
- Laws of indices come from powers: 23 × 22 = 25, because you're simply counting how many 2s are being multiplied.
A child who understands each step can almost work out the next one alone. A child who skipped a step has to memorise "add the little numbers" as a rule with no reason behind it. Rules without reasons are hard to remember and easy to misapply, and they fall apart the moment a question looks unfamiliar.
Maths is the clearest example, but this is true of nearly everything worth learning, including physics and chemistry, and including code.
How a Small Gap Turns Into Falling Behind
Nobody decides to leave a child behind. A teacher with a full class and a syllabus to finish has to keep moving, and a child who is lost rarely says so. Most learn to copy the steps and hope nobody asks.
For a while, that works. Then the next topic arrives, built on the one they never really understood. Now there are two things they don't follow. The topic after that depends on both. A gap that would have taken one good conversation to fix in March can look like "my child is bad at maths" by November.
From the outside, it looks like a child who suddenly can't keep up. In reality, the problem started months or years earlier, somewhere underneath the topic they're struggling with now. Extra practice on today's topic rarely helps, because today's topic isn't where the problem is.
What It Does to a Child's Self-Esteem
This is the part that worries me most. Children don't think, "I have a gap in my understanding of multiplication." They think, "Everyone else gets this and I don't." With nothing else to explain it, they decide the problem is them.
Once a child believes that, you start to see it in how they behave. They stop asking questions, so nobody thinks they're stupid. They rush through work to get it over with, or avoid it altogether. They say things like "I'm just not a maths person." And because they've stopped trying, they fall further behind, which seems to prove them right.
The sad thing is how often it isn't true. Plenty of children who have decided they're "slow" are perfectly capable. They were asked to build on something that wasn't there. Fill in the missing step and the next one makes sense, and few things rebuild a child's confidence like the moment something finally clicks.
How We Teach: Concepts Upon Concepts
This is how we teach at DotCode Campus, whatever the course, whatever the age. Here's what it means in practice:
- We start from what a concept is built on. Before introducing anything new, we ask what a student needs to already understand for it to make sense.
- We cover the basics thoroughly. Nobody is rushed past the simple ideas to reach the exciting ones, because the exciting ones are made out of them.
- We check understanding, not just output. A working program isn't proof. Being able to explain it and change it is. We've written about why explaining is the real test.
- If something hasn't landed, we go back. We look for the step underneath and fix that, rather than repeating the same explanation more loudly.
- Only then do we build. The new concept gets constructed out of the simpler ones the student already owns, so it feels like a small next step rather than a leap.
Small classes make this possible. With up to 6 students in a group, an instructor can see who's following and who's only nodding, and can stop to sort it out.
What This Looks Like in Our Courses
Here's a simple line of code that every programmer writes:
score = score + 1
To a child who hasn't properly understood variables, that line looks like a false statement. How can a number equal itself plus one? Teach them loops or game logic on top of that confusion and it spreads. So we make sure the idea is solid first: a variable is a labelled box, and this line takes out what's in the box, adds 1, and puts it back. After that, everything built on it becomes possible.
Every course is sequenced this way:
- Roblox Game Dev (ages 7–12). Students build a world first, then learn variables and events, then functions and loops. A leaderboard comes later because it needs all of those: a variable to hold the coins, an event to notice one being collected, and game logic to decide who has won.
- Python Programming (ages 12–16). Variables, then if/else decisions, then loops, then functions, then lists and dictionaries. A quiz game with a question bank near the end of the course uses every one of them.
- AI & Python (ages 13–17). Students begin with lists and loops, then count which word follows which, then add chance, then context, then turn words into numbers. By the time they reach ideas that sound advanced, each one is a small step from something they built the week before. They can carry on to AI Image & Video Generation, which picks up from their text generator.
The courses cover different subjects, but the principle never changes. That's also why the skills carry across. A child who truly understands a loop in Roblox doesn't have to relearn it in Python. There's more on that in what comes after Scratch.
Slower at the Start, Much Faster Later
Parents sometimes worry that spending time on the basics means falling behind other classes. We see it the other way round. Time spent on a foundation is paid back on every topic that sits on top of it, while time spent rushing has to be repaid later, usually with interest.
The idea isn't new, either. In 1968, the education researcher Benjamin Bloom described it as mastery learning: students should secure one unit before moving on to the next. Plenty of good teachers have always worked this way. I'd go further than most, though. Building each new idea on simpler ideas a child truly understands is, in my view, the only real key to learning. Everything else we do in a classroom, the games, the projects, the fun, works because of it.
How to Spot a Gap at Home
You don't need to know the subject to help. Try these:
- Ask "why?", not just "what's the answer?" If your child can get the answer but can't say why it works, the concept may be memorised rather than understood.
- Change the question slightly. A child who understands can handle a small twist. A child who memorised a method often can't.
- Listen for "I'm just bad at this." Treat it as a sign of a gap, not a fact about your child.
- Go back a step. If today's homework is a struggle, try the topic before it, then the one before that, until you reach what they're confident with. That's where to start rebuilding.
And when you find the gap, tell your child what you've found: "You're not bad at this. There's one piece we need to fill in." For a child who has been quietly blaming themselves, hearing that can matter as much as the maths.
Frequently Asked Questions
Why is my child falling behind in school?
Often it's because a concept they needed earlier was never fully understood. New topics depend on old ones, so a small gap shows up again in everything built on top of it. Other things can play a part too, such as attention, health or how a child feels about school, so it's worth speaking to their teacher if you're concerned.
Can a child who has fallen behind catch up?
Yes, in most cases. The key is to find the missing concept and fix it there, rather than doing more practice on the current topic. Once the foundation is solid, later topics often come together faster than parents expect.
What does "building concepts upon concepts" mean?
It means teaching ideas in an order where each one rests on simpler ideas the student already understands. Powers are taught after multiplication, and multiplication after addition. In coding, loops and functions come after variables.
Is spending more time on the basics a waste of time?
No. Fundamentals are used in every topic that follows, so time spent on them keeps paying off. Skipping them feels faster at first, and usually costs more time later.
Does this approach apply to every DotCode course?
Yes. Whether your child is making games in Roblox, writing Python or building a language model in our AI & Python course, the lessons are sequenced so that each new concept builds on the last. No coding experience is needed to start.
See How We Teach
The best way to understand our teaching is to watch it happen. Every course starts with a free 45-minute trial lesson, in a small group at our Jurong East studio or live online. Book a free trial class and see what learning looks like when no step gets skipped.
