01What coding classes for kids in Tashkent actually teach
In practice, two very different programmes are sold under the heading computer courses for kids. The first is digital literacy: the mouse, folders, a text editor, slides. The second is a programme where the child builds something of their own — a game, an animation, a website or a device that moves. Both have their place, but their schedules, length and results are completely different, so you cannot treat them as interchangeable.
One example makes the difference clear. In a slides lesson, the child drops a picture into a ready-made template — the result looks neat, but there is no logic underneath it. In a game lesson, when the character hits a wall and freezes, the child has to find the cause: a condition written incorrectly, blocks in the wrong order, or a mistake in the coordinates. That loop — it broke, find the reason, fix it, try again — builds a way of thinking that later carries over into maths, and even into planning an essay.
That is why the first question to ask is not "which software do you teach?" The better question is "a month from now, what will my child be able to build on their own, and can they show it to us at home?" If the answer is vague ("we give IT fundamentals", "they will learn the computer"), the core of the programme is probably just as vague.
02Age and experience: how to identify the right stage
This is where most mistakes happen: the child is placed not by age, but into whichever group has a free seat. The outcome is easy to predict — a six-year-old sits waiting for the teacher to read every line of text code aloud, while a thirteen-year-old gets bored of colourful blocks by the second lesson and concludes that "programming isn't interesting".
Beyond age, two more factors matter: can the child read, and have they seen code before? A ten-year-old who has spent a year in Scratch is ready for a text-based language; a classmate who has never written code will move into Python far more easily after a block-based stage first. The table below helps you compare the stages:
| Stage | What the child builds | Typical tools | Signs of readiness |
|---|---|---|---|
| From age 5 | Simple animation, character movement, a 3D scene | ScratchJr, Kodu, CoSpaces | Controls the mouse, recognises picture-based icons |
| From age 8 | Their own game, levels, an interactive world | Scratch, Construct 3, Roblox Studio | Reads the text on a block, remembers the rules of a game |
| From age 10 | A game in text code, a device with sensors | Python, Arduino and sensors | Looks for mistakes independently, is comfortable typing |
| From age 15 | A website, a mobile app, a data analysis project | JavaScript, Python libraries | Can carry a multi-week project through to the end |
Use the table to place your child in a stage, then compare that with the group you are being offered. If the course adviser asks about your child's age, reading skills and previous experience without being prompted, that is the first sign the programme is genuinely built in stages.
03Checking the tools when your child cannot read yet
Adverts almost never mention this point, yet for a preschooler it is decisive. Block-based programs are not all the same: some rely on pictures, others on written text.
In ScratchJr, commands are picture blocks — an arrow pointing right, a jump icon, a speech bubble. The child can make a character walk, jump and talk without reading a single word. That is why children who do not yet know their letters start with exactly this tool.
In Scratch and CoSpaces, by contrast, the blocks and menus are written in text: "move 10 steps", "if on edge, bounce". Here the child needs to be able to read the words, at least slowly, syllable by syllable. Otherwise they wait for the teacher to read for them at every step and cannot work independently.
The practical check is simple: when you call, ask directly — "which program will my child work in during the first month?" If your child is not reading yet, the answer should be ScratchJr. And if the main goal for now is reading, counting and attention span, a school readiness programme is a more logical starting point than a computer course — the child will then move into code much faster.
04Inside the lesson: group, rhythm and what the child keeps
Results come from how a lesson is structured, not from the name of the programme. A good session usually has three steps: the teacher demonstrates one technique on screen, the child repeats it, and then the child adds something of their own. Make sure that third step exists — "now give your character a second life yourself". Without it, the child has only been copying.
Pay separate attention to group size. A good group is one where the teacher can look at every child's screen within a single lesson. If two or three children share one computer and wait their turn, the slower child falls behind and the faster one gets bored — both lose out.
A practical rule on rhythm: regular short lessons work better than long sessions held rarely. For younger children it also matters that activities change within the lesson — work at the computer, discussion, a short movement break.
As for results, look at the folder. Is there a place where the child's own projects are saved — a folder or an online account? If after three months your child can show you three working projects, the programme is doing its job. If all that is left is notes in an exercise book, it is not.
05Before you call: a ready list of questions
One phone call or one visit is enough to get the essentials about a course. Ask the following questions in this order and write the answers down — comparing two or three places afterwards becomes easy.
Ask when you call the course:
- Which stage suits my child's age and experience — and what are you basing that on?
- Which program will my child work in during the first month? (For a child who cannot read yet, the answer should be a picture-based tool.)
- How many children are in the group, and how many children share one computer?
- How long is a lesson, and how many times a week does it run?
- What does my child take away from a lesson — where are their projects saved?
- Is there a next stage after this course, and where does the child move on to after a year?
- What experience does the teacher have working with children of this age?
- Can we come to a trial lesson and see the room where lessons are held?
Specifics matter in the answers. "We will choose the right course for your child" is not an answer; "if your child has worked in Scratch, we move to a text-based language, otherwise we start from the block stage" is an answer.
06Warning signs and the parent's role
If you come across any of the following, take your time and reconsider the decision:
- nobody asks about the child's age or reading skills — everyone gets the same programme;
- the lesson is only theory, or only typing practice;
- you are promised a "ready-made developer" in a short time;
- questions about the teacher's experience with children are sidestepped;
- you are not allowed a trial lesson or a look at the classroom;
- the programme is not divided into stages — nobody can say what the child will be doing a year from now.
What to do at home
The course is only half the process. Once a week, play your child's project and ask "how did you do this?" — explaining it cements what they know. Do not call code that does not work a failure: finding mistakes is how programming works, so "come on, let's look for the reason together" is a far more useful tone. And do not compare the result with other children: one child loves making games, another robots, a third animation — where the interest is, the child learns on their own.
07How this is organised at Singapore Skills Academy
If you are looking for IT courses for kids in Tashkent, the Timedoor Academy programme at Singapore Skills Academy is built around exactly these criteria: ages 5 to 18, with coding, robotics and artificial intelligence combined into a single path.
The stages run as follows: Junior Coder (ages 5–7, ScratchJr, Kodu, CoSpaces, Scratch 3.0), Code Adventure (ages 8–14, Scratch, Construct 3, Roblox Studio), Python Developer and IoT & Robotic (ages 10–15), Software Engineer and AI Engineer (ages 15–18). Groups hold up to 6 students, each lesson lasts 60–90 minutes, and lessons run 1–2 times a week.
If your child cannot read yet, or if school readiness is the main goal, the school readiness programme may be a more logical place to start. Which stage fits a child cannot be guessed from a distance — that is what the free consultation and free trial lesson are for, and you can request them through the form on the site.

