"My kid is too young to learn coding."
This single sentence is probably the most common one. The parent pictures "coding" as typing code and assumes you need to be 12 years old with a serious math foundation.
RealityA 3.5-year-old can learn coding concepts — but without a screen and without code. Lego, Tale-Bot, cards you line up so the robot goes where you tell it. More on this in our article on robotics for preschoolers. The goal isn't for a 4-year-old to write a Python program — the goal is to learn what a "command" and a "sequence" are.
"You have to be strong in math to be able to code."
A logical assumption — coding looks like math. Parents whose kid "isn't great at math" assume the class is lost before it begins.
RealityCoding for kids (from Scratch to AI) looks more like storytelling than math. The kid tells a story, the character moves, events happen, conditions exist. The math used is addition and subtraction — which a six-year-old already knows. Many of our most successful students aren't "math geniuses" — they're impatient makers who want to build something.
"It's more for boys."
Statistics in the IT industry still show a gender imbalance. Parents project this back onto kids' classes and assume it reflects interest.
RealityHalf of our students are girls. At young ages, social dynamics aren't split into "boy" and "girl" interests — a kid who loves to build builds with anyone who builds. Pushback against STEM in girls usually comes later, around high school, and it doesn't have to. More on this in a separate article.
"Coding is a lot of sitting in front of a screen — it'll be a health problem."
Parents who try to reduce screen time, with reason, hesitate over a class that's "in front of a screen".
RealityThe youngest students (under 5.5) have no screen — they work with Lego bricks, physical robots, and cards. Older kids do use a screen, but in the context of building, not passive watching. Plus, one class a week (60 min of screen) is less than 1% of the average weekly screen exposure of today's kid. The other YouTube the kid watches while you wait to leave for school is the real problem — not a coding class.
"If they learn this, they have to become a programmer."
Parents enter the class thinking it's a "career path" and feel the pressure.
RealityProbably 1 in 5 of our students ends up in IT. Most go in completely different directions — medicine, acting, languages, sports. And that's perfectly fine. Coding is a skill that changes how a kid thinks, not what they will do. A kid who coded for 3 years will run a shop better, organize a schedule better, even fish better — whatever. Ways of thinking transfer.
What's actually true about the risks
Two real "risks" of a kids' coding class, to be honest about them:
- The wrong class can put a kid off coding forever. A poorly run course, a kid too young for the group, an impatient teacher — and the kid leaves with a "coding is boring" experience for 5 years. Choose carefully. A free trial is mandatory.
- A class doesn't work on its own. If the class is the only place the kid "builds anything" while they passively consume content the rest of the time, the benefit is limited. The biggest effect shows up when the class spills over into everyday life — the kid spontaneously opens Scratch on a weekend.
If you're still unsure after this article — that's good. The free trial exists exactly for that. 45 minutes, your kid in a real situation, then an honest opinion from the teacher. No commitment. There are answers there that theoretical articles can't give you.
DigiKids Vračar — coding and robotics for ages 3.5–13. See our programs or book a free trial.