He said “I can’t” four times in the first session. Not to me. To himself, quietly, after each attempt. The first time he said it he pushed back from the screen. I let him. He came back three minutes later.
By week six, he stopped saying it. Not because anyone told him to stop. Because he had run out of problems that stayed impossible long enough to justify the phrase. It had become inaccurate, and he knew it.
The shift from “I can’t do this” to “let me try again” is the most important developmental event that happens in a technology program. It is not a technical milestone. It is a cognitive and emotional one. And it does not happen on a schedule.
What the Shift Actually Looks Like
It does not announce itself. It is usually invisible to the child when it first happens.
The first visible signal is the pause. The student hits a problem. Instead of immediately asking for help or closing the screen, they pause. Just a moment. Then they try something. The pause is the shift beginning. It is the interval between “this is impossible” and “what if I try this instead.”
What I watch for in the first months of enrollment is how that pause changes. At week two it might be two seconds. At week eight it might be two minutes. At month six the student might not even be aware they are doing it. The habit has become background.
That small change in behavior, a pause before giving up, is one of the most durable things a program can produce in a child. It carries into every environment they enter after this one.
What Causes the Shift
The shift happens because the environment makes it possible to fail small and try again immediately. In a coding session, the feedback loop is short. A student tries something. It does not work. The screen tells them specifically what did not work. They try something else. The interval between attempt and feedback is seconds.
That compressed feedback loop is what most learning environments do not provide. In school, a student submits work and waits. In a coding session, the error message arrives instantly and the student can respond to it right then. The speed of the loop is what makes the try-again habit form faster than it would anywhere else.
The other factor is that failure is structurally normal in a well-designed technology program. Nobody celebrates a clean first attempt in a way that makes a failed first attempt feel like a problem. The students who have been enrolled longer model the try-again response openly. The coach asks “what did you try?” rather than “why didn’t it work?” Those cues accumulate over weeks into a different relationship with difficulty.
Why It Transfers Out of the Program
The shift transfers out of the coding environment because it is not actually about coding. It is about the student’s relationship to difficulty. A child who has rehearsed the try-again response hundreds of times in a coding session carries that response into homework, into sports, into friendships, into anything that does not immediately go the way they intended.
Persistence is not domain-specific. A student who has built the habit of staying with a problem in a coding environment does not leave the habit behind when they close the laptop. It goes with them.
Parents describe the transfer in specific terms. Their child stayed with a math problem for ten minutes without asking for help. Their child tried three different approaches to a conflict before coming to them. Their child watched a video on how to fix something rather than asking an adult to do it. Small moments. Real signals.
What Programs That Produce This Shift Do Differently (Sandra)
The programs where this shift happens reliably share specific structural features. Feedback loops are short. Failure is normalized at the session level, not just in the mission statement. Coaches ask “what have you tried?” before offering any guidance, which means students cannot outsource the first attempt. And the progression framework makes trying again the obvious next move rather than a choice the student has to manufacture.
A belt system that advances students based on demonstrated persistence alongside technical skill is a system that rewards the try-again response at the structural level. The student who gives up and asks for the answer does not advance the same way the student who stays with the problem does. That structural signal accumulates across dozens of sessions into a behavioral norm.
The programs parents keep talking about long after their child has moved on are almost always the ones where failure had a defined, normal place in the session design. Not failure as a setback. Failure as the mechanism through which learning happens.
What Can Slow the Shift Down
The shift from “I can’t” to “let me try again” is not inevitable. It depends on conditions. When those conditions are absent, the shift either does not happen or takes much longer.
The first condition that slows it down is a coaching culture that moves too quickly to give answers. A student who asks for help and receives the solution immediately learns that asking is faster than trying. That is accurate. The habit forms accordingly. Programs that produce the shift reliably are programs where coaches consistently ask “what have you tried?” before offering any guidance. Not as a technique. As a genuine question. The student has to account for their own attempts first.
The second condition is a peer environment that rewards getting it right more than it rewards trying. In a room where the status goes to the students who produce working code quickly, a student who is still on their third failed attempt has social incentive to stop. In a room where the norm is “keep going,” the same student has social permission to stay with the problem.
Both of these conditions are structural, not individual. A child who has not made the shift is not less capable than a child who has. They may simply have not yet been in an environment where the shift was structurally supported. That is the variable that matters.
What the Try-Again Habit Looks Like as It Settles In
The habit does not arrive all at once. There is a period, usually around months two and three, where the student is in transition. They try again sometimes. They still give up sometimes. The difference is that the giving-up episodes become shorter. The restart comes sooner. The student is learning, at the structural level, that giving up is a temporary state rather than a final verdict.
By the six-month mark, the students who are building the habit reliably have one thing in common: they have experienced enough successful recoveries from failure that the evidence has accumulated. They have tried again and it worked often enough that “let me try again” has become a strategy, not a hope.
That evidence base is what makes the habit durable. It is not built on encouragement. It is built on proof. The student has a record of figuring things out, and the record is what they draw on when the next hard thing arrives.
For Gladstone Families Watching for This Shift
Parents from Gladstone who enroll their children at Love to Code Academy at 248 NE Barry Road often ask when the shift happens. The honest answer is that it is different for every student, and it rarely announces itself when it arrives.
Watch for the pause. The moment between encountering a problem and deciding what to do with it gets longer. The student starts sitting with difficulty rather than escaping from it. That is the shift, and it happens in a coding session first. Then it starts showing up everywhere else.
The after-school program at LTCA is built to produce exactly that. Not as a side effect of teaching coding. As the primary purpose of the session design.
