Coding for kids in Vračar — the complete parent's guide

1. Why coding for kids at all?

Before we get to "which language" and "from what age", we need to answer the real question: why? Because if the reason is "everyone else is signing up" — your child will probably bail on it pretty quickly.

Our take, after five years of teaching kids in Vračar, is that coding gives a child four things:

1. A different way of thinking. Coding teaches kids to break a problem into smaller steps — useful for maths, languages, chess, even packing a school bag in the morning.
2. Tolerance for mistakes. At school, a mistake is a red mark on a test. In a program, a mistake is "it doesn't work, let me see why". Big difference.
3. A sense of agency. A child who builds their own game — not plays someone else's, but builds one — sees screens differently. The screen is no longer a magical glass window; it's something they can control.
4. Preparation for the world they'll live in. No matter what profession they end up in, today's seven-year-old will be working with software for life. The question is whether they use it passively or understand how it works.

If none of these reasons feel important for your child — okay, coding probably isn't a priority. There are plenty of useful activities: music, sports, languages. Coding is just one option. Not a magic wand.

2. What age is realistic?

The most common question we get. The honest answer: from 3.5 years we can do something meaningful — but it's not what most parents picture as "coding".

3.5 to 5 years — no screens

At this age there's no "coding" in the literal sense. There's learning logic — through physical blocks, robots that follow card-based commands, Lego builds. The child learns the concept of "command" and "sequence" before seeing a single line of code. That's the heart of our Legići program.

5 to 7 years — Scratch Junior

This is where the real work begins. Scratch Junior is a visual language where "commands" snap together like blocks on screen — no typing, no syntax. A six-year-old can put together a small animated project in a couple of sessions. Our Yellow Belt lives here.

7 to 11 years — full Scratch + Micro:bit

This is the "golden age" for an introduction to coding. The child is old enough to grasp variables and loops, and young enough not to resent having to learn. Scratch + physical hardware (Micro:bit boards, small robots) — a combo that holds attention.

11 to 13 years — text-based coding

Here we move into Python — the first "real" language they actually type. Black Belt. This is where the difference shows between kids who are genuinely interested in coding and kids who enjoyed it up to a point. Both outcomes are fine.

If you're thinking about getting your six-year-old to "learn Python so they have an edge in high school" — please, don't. A six-year-old doesn't need Python. A six-year-old needs to enjoy the process so that, when they turn eleven, Python is a natural next step.

3. Which language first?

The most common misconceptions we hear:

• "Python because it's popular at work." Yes, but for adults. For a nine-year-old, Python is too text-heavy, too abstract.
• "JavaScript because it's for the web." Same problem — the syntax is unforgiving for a beginner.
• "C++ because it's serious." Absolutely not. Even adult beginners struggle with C++.

Our progression — proven in the classroom and backed by research from the MIT Lifelong Kindergarten group — is:

1. Physical "languages" (Lego, Sphero) for ages 4–6. You arrange cards, the robot moves.
2. Scratch Junior (5–7). Visual blocks, simple logic.
3. Scratch (7–11). Visual, but with all the concepts of real programming.
4. Python (11+). Text-based, clean syntax, useful long term.

Every shortcut we see (e.g. "the kid is 7, let's go straight to Python") usually ends the way you'd expect — frustration within three weeks.

4. What coding for kids isn't

To be straightforward, here's what coding for kids doesn't do:

• It doesn't turn kids into engineers. About 1 in 5 of our students later goes into IT. That's perfectly normal and not a failure.
• It doesn't reduce screen time. If your child is spending too long on YouTube, two hours of Scratch a week won't fix that. Different problem.
• It doesn't make "smarter kids". IQ doesn't shift because of coding. Ways of thinking do — but that's not the same as "smarter".
• It doesn't replace maths, sports or socialising. Coding is one activity. It can't be the only one.

5. Five signs it's clicking for your child

After the first few sessions, here's what we look at to gauge whether the program suits a particular child:

1. The child asks "what's next?" — that's the best sign. They're asking for a new block, a new feature, a new challenge.
2. They mention class at home. Doesn't have to be about the material — it's enough that they bring up the teacher, a classmate, something they did.
3. They go back to their projects. They open Scratch on their own and pick up where they left off. Nobody told them to.
4. They push through the boring bits. Coding has dull bits (you have to set up a variable, you have to find the right block). A child who powers through that for something they care about — good sign.
5. An error doesn't break them. When something doesn't work, they say "hold on, let me see". No tears, no quitting. It's a mindset we teach, but some kids already have it naturally.

If you see 3 out of 5 — go for it. If 0 out of 5 — try again in 6 months, or look at a different activity.

6. Coding in Vračar — where and how

There are several options in Vračar. We'll be straightforward: if our program isn't right for some reason (age, schedule, location), we'll tell you. Better for everyone if you go to the right place than to pay us and then drop out.

Things to look for when choosing:

• Group size. Above 8 kids, the teacher can't give each one proper attention. Our cap is 6.
• Whether they use proper tools. Lego Education, BBC Micro:bit, MIT Scratch — these are the standards. "Some unknown homemade kids software" is a red flag.
• Class length. 60 minutes is the sweet spot. Less is too little; more is too much.
• Location. Max 15 minutes' walk from school or home — any more and the kids are tired and cranky before they arrive.

7. What to ask at the trial class

Five questions that always pay off:

1. "What won't my child learn here?" An honest teacher knows the limits of their program.
2. "How quickly will you see whether it's right for them?" Two or three sessions is enough for any experienced teacher to tell.
3. "What do you do if a child gets bored?" Differentiated tasks — that's what you want to hear.
4. "What if a child is shy and hangs back?" Patience, and bringing them back to the level where they feel safe — that's the answer you want.
5. "Can I sit in on the first class?" Yes. From the side, not getting involved.

Wrap-up

Coding for kids isn't a magic wand, but it isn't a fad either. The right program at the right time, with the right people, can be one of the best activities you'll give your child. Wrong fit — and it can put a child off coding forever.

Our advice: bring them once, watch from the side, listen to them on the way home. Everything else — program, language, schedule — matters less than that.

Written by the DigiKids Vračar team. If there's a topic you'd like us to cover, drop us a line at digikidsvracar@gmail.com.