The Process of Learning

Parents often assume learning ability is fixed—some kids are "naturally" good at math or coding, and others simply aren't. But learning is itself a skill, one that follows a fairly well-understood process in the brain. Much of what we now know about this process comes from cognitive scientist Barbara Oakley, whose Coursera course, "Learning How to Learn," is one of the most enrolled online courses in the world. Her work, much of it also outlined in her book "A Mind for Numbers," breaks the mystery of learning down into concrete, teachable mechanics. Here's what that process actually looks like and how it plays out when a child is learning something like coding or robotics.

Two Modes, One Brain

One of Oakley's central ideas is that the brain works in two distinct modes: focused mode, where you're concentrating hard and directly following a familiar train of thought, and diffuse mode, a more relaxed, wide-lens state where the brain makes unexpected connections between ideas. Her course introduced this distinction between focused and diffuse mode thinking as a challenge to conventional study habits. You cannot be in both modes at once—but real learning requires moving between them.

For a child stuck on a stubborn coding bug, this explains something every parent has seen: banging your head against a problem for an hour often does less than stepping away for ten minutes to do something completely different. The diffuse mode keeps working in the background, and the solution often arrives the moment the child stops "trying." This is why a short break even just a walk or a snack—is a legitimate learning strategy, not a distraction from one.

How the Brain Builds Complexity from Simplicity

Oakley also emphasizes the concept of chunking—grouping related pieces of information into a single, compact mental unit so the brain can handle them as one thing instead of many. Chunks form through experience, becoming stronger and larger over time, and connect with one another during diffuse mode to help solve new, unfamiliar problems

This is essentially how coding is taught well. A child doesn't learn "variables," "loops," and "conditionals" as thirty separate rules—they learn them as one chunk: "how a sprite moves and reacts." Once that chunk is solid, it becomes a building block for the next, more complex one, like combining loops and conditionals to build a mini-game. This is also why progressive, level-based curriculum works better than throwing every concept at a child at once—the brain needs one chunk locked in before it can comfortably absorb the next.

Practice Over Passive Review

A common trap for both kids and adults is mistaking recognition for understanding—rereading notes or watching a tutorial again and feeling like you "get it," when in reality you'd struggle to reproduce it from scratch. Oakley's course stresses retrieval practice actually testing yourself as far more effective than passive review, along with the importance of avoiding the "illusion of competence" that comes from just rereading material.

For a child learning to code, this means the real learning happens when they close the tutorial and try to build the project unaided, not while they're following along step by step. Struggling to recall a function's syntax and getting it wrong is often more valuable than reading it correctly for the third time—the friction is where the memory actually forms.

Why Cramming Doesn't Work

Two more concepts from the course matter here: spaced repetition (revisiting material over gradually increasing intervals rather than all at once) and interleaving (mixing different types of problems instead of drilling one skill repeatedly). Oakley's course covers spaced repetition and interleaving as techniques for making practice stick and adapt across contexts, from math to music to physical skills.

This is why a coding course spread across weekly sessions, revisiting earlier concepts as it introduces new ones, tends to produce far more durable skills than a single intensive weekend. A child who learns loops, sets them aside for two weeks, then uses them again inside a new project retains that concept far better than one who used it once and moved on.

Procrastination Isn't Laziness—It's Pain Avoidance

Oakley also addresses why kids (and adults) procrastinate: the brain treats a difficult, unfamiliar task as mildly painful and looks for an escape. Her practical fix, drawn from the course, is the Pomodoro Technique—short, timed bursts of focused work (typically 25 minutes) followed by a real break. This lowers the psychological barrier to starting, since the child only has to commit to 25 minutes, not "finish the whole project."

For a parent, this translates into a simple, usable tactic: instead of telling a child to "practice coding for an hour," set a 25-minute timer for one specific, small task—finish this one function—and let them stop guilt-free when it rings. Small, repeated wins build the same skill an hour of dread-filled procrastination never will.

Sleep and Downtime Aren't Optional Extras

One point Oakley returns to often is that sleep plays an active role in memory consolidation—the brain replays and strengthens what was learned that day during sleep and can even flush out toxic byproducts of neural activity that build up during waking hours. A child who pulls a late-night cramming of a coding concept before a class is often working against their own brain rather than with it. A full night's sleep after a hard learning session isn't a break from learning—it's part of it.

Why This Matters More in STEM and Coding Than Almost Anywhere Else

Coding and STEM subjects are unusually well-suited to Oakley's framework because they're inherently cumulative—you cannot understand functions without first understanding variables, and you cannot build a working robot without understanding the individual sensors and motors first. This is exactly why a project-based, progressively structured approach (build something small, chunk that skill, revisit it, build something slightly bigger) mirrors what the science says actually works, rather than a model built around long lectures and one-off tests.

Programs like The STEM Educators are built around this same idea in practice—project-based learning where kids build something new almost every session rather than sitting through theory, and a progressive curriculum where each course deliberately builds on the last so that skills form in the right order and get revisited as they grow. That structure isn't a stylistic choice—it's essentially spaced, chunked, interleaved learning applied to coding.

Turning the Science Into a Habit

None of this requires a child to become a neuroscience expert. It just means restructuring how they approach hard material: work in short focused bursts, take real breaks, test yourself instead of rereading, come back to old material instead of abandoning it, and treat sleep as part of the process, not an interruption to it. Once a child (or a parent guiding them) understands why they're struggling—rather than assuming they're "just not good at this"—the frustration usually drops, and the actual learning speeds up.