A parent told me once that she knew something was different on a Tuesday evening in October. Not because of anything that happened at the program. Because her son sat with a math worksheet for twelve minutes before asking for help, and he had never done that before. Not once.
She had not been told to watch for that. She just noticed it. And then, once she noticed it, she started noticing other things. The way he described a problem at dinner. The way he came back to something he had given up on the day before. Small things, one after another, that added up to something that felt significant.
The growth from a character-based technology program does not show up in a project showcase. It shows up at home, in small moments, in places parents were not looking.
The First Place It Usually Appears
The first behavioral change parents typically notice is in how their child handles something that does not immediately work. This is the persistence signal, and it appears before any other signal because persistence is the skill the program builds most directly and most explicitly.
Before: a child who encountered a hard problem and either gave up quickly or immediately asked for help.
After: a child who pauses. Who tries one more thing first. Who has not changed their emotional response to frustration, but has changed what they do with it.
That is a small change. It is also one of the most significant developmental shifts a parent can observe in a child, because it signals a different relationship to difficulty. Not the absence of frustration. A different decision about what to do when frustration arrives.
What to Watch for in the First Three Months
Growth in the early months is quiet. The child is still calibrating to the environment, building familiarity with the tools, learning the social norms of the session. The internal work is happening before the external signals appear.
The most reliable early signal is not skill-based. It is the description the child gives of their sessions. A child who comes home and says “I fixed the bug” or “I couldn’t figure it out but I tried three things” is narrating their experience in a way that signals healthy development. The presence of failure in the narration, described matter-of-factly rather than with shame or avoidance, is one of the clearest early indicators that the program’s culture is working.
A child who comes home and only reports successes, or who does not want to talk about the session at all, is worth a check-in with their coach. Not necessarily a problem. But worth a look.
The Six-Month Mark
Around the six-month mark, the character development signals become more distinct. Parents in this range describe three consistent patterns.
First: their child is more patient with themselves during difficulty. Not perfectly patient. But the frustration-to-shutdown interval has lengthened. There is more space between “this is hard” and “I’m done.”
Second: their child narrates their own problem-solving. At dinner, they describe what they tried. Not what they built. What they tried. That narration is evidence that the metacognitive habit, the practice of examining your own thinking process, has started forming.
Third: their child is more willing to try something they have not done before. The terror of being a beginner, which most K-2 students carry into the first session, has become something smaller. Not gone. Smaller.
What the One-Year Signal Looks Like (Sandra)
At the one-year mark, the pattern becomes something parents can name. It is not a collection of small signals anymore. It is a quality of character that is observable across multiple contexts.
The programs parents keep talking about long after their child has moved on produce a specific kind of student. Not a student who can code. A student who handles hard things differently. More patient with uncertainty. More willing to try and fail and try again. More honest about what went wrong and more interested in what to do about it.
That pattern is not accidental. It is the output of a program that was designed to produce it, tracked it explicitly at every belt level, and made it as visible and measurable as technical skill. The parent who watches for the signals described here will see them. They do not announce themselves. But they are there.
Questions Worth Asking Your Child After Each Session
The growth that happens inside the session becomes more visible at home when parents know which questions to ask. The default question, “how was it?” returns the default answer, “fine.” A more specific question returns a more specific answer, and a more specific answer reveals what is actually developing.
The question that surfaces the most meaningful information is not “what did you build?” It is “what were you trying to fix?” A child who can answer that question with specificity, “the robot kept turning the wrong way and I tried adjusting the turn value three times before it worked,” is showing metacognitive development. They are narrating their own problem-solving process. That narration is evidence that the process has become conscious enough to describe.
A second useful question is “was there anything you gave up on?” Not as a challenge. As a genuine inquiry. A child who can say “yeah, I couldn’t figure out the sensor part, I’ll try something different next time” is demonstrating something more valuable than a child who reports only successes. They are describing a healthy relationship to incomplete work. Not shame. Not avoidance. A plan.
The child who cannot yet answer these questions without deflecting is also giving information. The growth toward being able to narrate difficulty honestly is itself a developmental arc, and it is worth tracking.
When to Check In With the Coach
Most parents do not check in with their child’s coach often enough, not because they are disengaged but because the sessions seem to be going well and there is no obvious reason to. The most valuable check-ins happen not when there is a problem but when there is a pattern worth understanding.
A useful check-in question for the coach is: “What is she working on that is genuinely hard for her right now?” Not “is she doing well?” That question invites a summary. The specific question about what is genuinely hard invites insight into where the character development is actually happening. The answer will tell a parent what problem-solving the child is practicing, and it will help the parent know what to watch for at home.
A second useful check-in question is: “What does she do when she gets stuck?” The answer reveals the try-again habit in its current state. A coach who says “she asks for help right away” is giving different information than a coach who says “she tries a few things first, then asks.” Both are useful. The first signals where the work still is. The second signals progress that may not yet be visible at home.
For Parkville Families Paying Attention
Parents from Parkville who are enrolled or considering enrollment at Love to Code Academy at 248 NE Barry Road are close enough that the sessions become a regular, low-friction part of the week. That regularity matters. The growth described here is cumulative. It builds across sessions, not within them.
The after-school program at LTCA was built to produce the outcomes described above: not in theory, but in the specific behaviors that parents can actually observe. The coding is the mechanism. The growth is the destination. And the growth shows up at home, in small moments, usually before anyone names what they are seeing.