First, let's clear up what we're looking for
"My child is into it" doesn't mean "my child is a genius". It doesn't mean "my child will be a software engineer". And it definitely doesn't mean "my child will be at the IT olympiad at 14".
"Into it" means: the child enjoys the process, makes age-appropriate progress, and starts wanting to explore on their own. That's a perfectly good benchmark — and quite different from what parents often picture.
So, signs your child is into coding:
5 signs YES
✓ Good signs
- They ask "what's next?". Not "I'm bored", but asking for the next challenge.
- They open a project at home on their own. Nobody told them — they remembered, they wanted to finish it.
- An error doesn't break them. "Aha, here's the problem" instead of "I'm done".
- They talk about it at home. Mention the teacher, a classmate, what they did.
- They come back to their work. Open the same project for several weeks running, slowly building it up.
✗ Signs maybe not
- They constantly complain before class. After 4–5 sessions, still inventing a "headache" beforehand.
- They don't know what they did. After class, asked "what did you make?" — "nothing, something".
- Tears after the first error. A mistake becomes a catastrophe, not a challenge. For months.
- They never open it on their own. After 6 weeks — not once at home.
- Not a single friend from the group. They don't mention anyone, no connections form.
The signs in more depth — what they really mean
Sign: the child asks "what's next?"
The best sign. Here's why it matters: in coding, everything is open-ended. There's no "end of the textbook". A child asking for the next challenge is internally motivated, and they'll keep moving forward regardless of us.
Sign: opens a project at home on their own
This one is decisive. If, after class, the child opens Scratch (or whatever tool) without being prompted, just to fix or continue something — it's a sign that it's "clicked". Doesn't have to be every day, doesn't have to be for long. A few times a month in the first few weeks is enough.
Sign: an error doesn't break them
Coding is 70% errors. Literally. Professional developers spend more time debugging than writing. If a child can't tolerate mistakes, coding will feel exhausting — no matter how "smart" they are.
Good news: tolerance for mistakes is something you can learn. It's also one of the things we work on in class. But kids who already have a baseline of patience start with an advantage.
And the signs that maybe not — and what to do
Sign: constant complaints before class
A seven-year-old who doesn't want to go to piano might just not want to go to piano. A seven-year-old who doesn't want to go to piano, sports, or school — there's probably something deeper going on than any one activity.
But if after 5–6 coding sessions they're complaining as much as after the first one — the activity isn't for them. Have a conversation. Maybe a break is needed. Maybe a different kind of activity. Maybe it's too early (3.5 is a realistic minimum, 5 is the "comfortable" minimum).
Sign: doesn't know what they did
Heads up: don't confuse this with "the child can't articulate". A five-year-old may not know how to describe what they did — that doesn't mean they weren't engaged. Ask from a different angle: "Show me something next time we finish." Or: "Who was sitting next to you?" Specific questions reveal more.
Sign: not a single friend
This one is maybe the most powerful "teacher" in any activity — friends. A child who builds a social bond with someone in the group is a child who has a reason to keep coming, even past the occasional dull moment in class. A child who hasn't mentioned a single name after 8 weeks — something's missing.
What to do if you see "red flags"
- Open conversation. "I can see you're not really enjoying it. What do you think?" No accusation, no leading the answer.
- Talk to the teacher. The teacher often spots things a parent doesn't — and vice versa. Compare notes.
- A pause, not a quit. 2–3 months off, then come back. Often a child grows into an activity they weren't ready for.
- Change of group. Maybe the group is wrong (too young, too old, personality mismatch). Switching groups can fix it.
- Calling it — that's OK too. Coding isn't for every child. Sport isn't for every child. Piano isn't. Nobody has to do anything.
A good coding programme isn't one that keeps every child. A good coding programme is one that honestly says "I don't think this is for your child" when they see it. We do this. And we're still in business.
Special cases worth mentioning
A child with ADHD
Coding often works surprisingly well. The fast feedback (I clicked, I see what happened) holds attention better than a classroom does. But not every child with ADHD reacts the same way. Try it. Judge honestly.
A child on the autism spectrum
Coding is often one of the best activities — structured, predictable, clear rules. But the social side (working with classmates) can be a challenge. Talk to the teacher before signing up.
A shy child
Don't give up early. Shyness melts away within 4–6 sessions for 80% of kids. Try a small group (we cap at 6).
A child who already knows "some" coding
If your nine-year-old says "I already know Scratch" — believe them and bring them in to see us. We'll place them in the right group, not send them back to a level they've already cleared.
Most important: don't rush to a conclusion
After the first session it isn't possible to tell. After the second — maybe. After 4–5 — usually.
The typical arc: first class — the child is passive, watches. Second — starts doing things. Third — asks questions. Fourth — knows the teacher's name and a classmate's. Fifth — starts building something of their own. Sixth — opens a project at home.
If that curve isn't happening — let's talk. If it's happening more slowly but it's happening — give it time. Every child moves at their own pace.
At DigiKids Vračar, after 4–5 sessions the teacher gives the parent an honest opinion. If the program is right for your child — we say so. If it isn't — we say that too.