One tutor sitting beside one child, starting from the project already open on their screen. Blocks first, written Python when the child is ready, and a note you can read after every session.
Coding for kids is one-to-one tutoring in programming for children roughly seven to fifteen, taught beside the child's own laptop in Bangkok or through a shared screen anywhere in the country. Lessons begin in block editors such as Scratch and move into written Python once the child reads and types comfortably. Every session ends with something that runs.
Screen work is easier to share than a textbook, so the format matters less here than in most subjects. Choose by the child's schedule.
Wherever the child's laptop already lives: the dining table, the study room downstairs, a quiet corner of the café on the corner. The tutor sits beside the child and never takes the keyboard.
Screen sharing, with the child typing and the tutor watching. For a beginner this is often better than in person, because the code stays under the child's hands.
Siblings or classmates who already build things side by side. They keep separate projects and help each other read errors.
Bangkok teaches two school systems at once, and computing turns up at a different moment in each of them. The tutoring follows whichever one your child actually attends.
Under หลักสูตรแกนกลางการศึกษาขั้นพื้นฐาน พุทธศักราช 2551 (ฉบับปรับปรุง พ.ศ. 2560), technology belongs to the วิทยาศาสตร์และเทคโนโลยี learning area. A primary child usually meets it in a shared lab with one screen per two pupils, which is enough to follow along and rarely enough to finish anything.
Subjects:
Focus Areas:
By lower secondary most children read fluently enough to meet a language with rules. This is where a tutor is worth most, because the first error messages arrive here and a class of forty cannot stop for one child's traceback.
Subjects:
Focus Areas:
Computing sits in the timetable from the early years, taught in English and assessed by the school's own descriptors rather than a national paper. The pressure arrives in Year 9, when the child chooses whether to carry the subject into IGCSE.
Subjects:
Focus Areas:
There is no national syllabus for private coding lessons, so the order below is ours: each block is a thing the child can do at the end of it, in that order, because each one depends on the one before.
A child who already builds games in Scratch skips the first block. The first session decides where to start, and moving on early is normal.
Scratch hides the typing and keeps the thinking. Everything here reappears in Python later under a different name, which is the whole point of starting at this end. The block closes with two signals: messages passing between sprites, and the day the project becomes a wall of blocks nobody can read.
The move from dragging to typing is where most children stall, so it gets its own block and a slow pace. Nothing in it is hard; all of it is unforgiving about spelling. It opens with print and input, and why the program stops and waits, and ends with the child writing one function and calling it twice.
Block editors never crash, so a child arriving from Scratch has never been told off by a machine. The first red paragraph is an emotional event before it is a technical one, and it is taught as a skill. Two habits carry the rest: say the broken line out loud before touching it, and keep a working copy before any big change.
Children stay for the game. This block turns the wish into a structure: a loop that keeps running, input that arrives while it runs, and a rule for stopping. The quiet discipline underneath is saving and reopening without losing the thread, and finishing the project instead of starting a better one.
The point where coding stops being a toy: the child writes something the household actually uses, a chore the family really has, and then tests it with the awkward input that breaks it. It is also the first time the work survives past the session.
Everything a child posts is public by default. This block is short, and it is the one parents ask about most once the child starts publishing. It finishes with housekeeping that matters later: dated copies so nothing is lost, and what a folder of finished work looks like at this age.
Four families who arrive with very different questions, and get different first sessions.
You cannot tell whether your child is learning or watching videos, and nothing in the report card helps. This is the most common reason families call.
Recommended:
Forty pupils, twenty screens, one teacher, and a child who follows along without ever finishing anything of their own.
Recommended:
Computing has been on the timetable for years and is about to start carrying marks. The choice at the end of Year 9 is real, and it is easier to make from evidence.
Recommended:
They built games for a year from video tutorials, then hit something the videos do not cover, and quietly stopped opening the editor.
Recommended:
Code is hard to judge from the doorway. The note is written so a parent who has never programmed can still tell whether the hour went well.
A sentence naming the thing that exists at the end of the session, and whether it runs. Topics covered mean little at this age; a finished thing means a great deal.
Which error held the session up, and how it was found. This is where the learning actually happened, and it is the part a child forgets to mention at dinner.
A single change small enough to do alone in twenty minutes. Not homework, and never something the child needs help to start.
The project itself, so you can press play. Parents who can run the thing ask better questions than parents reading a description of it.
Ability is rarely the cause of any of them. Each has a moment in the year when it tends to arrive, and a way out that costs nothing to take.
Why it happens
In a block editor nothing ever crashes: a wrong block simply does nothing, and the child keeps their confidence. The first time they type Python, the screen answers back with a paragraph in red, and a nine-year-old reads that as being told off rather than as information.
How we fix it
For the first month of text code, every session opens by breaking something on purpose and reading what the machine says back. An error stops being a verdict and becomes the fastest way to find the line.
Why it happens
The 2560 revision of the national core curriculum moved technology into the วิทยาศาสตร์และเทคโนโลยี learning area; before it, the subject sat in การงานอาชีพและเทคโนโลยี with the practical and vocational work. So the mark rarely arrives home labelled computing, and parents look for the cause in the wrong subject.
How we fix it
The first session asks which learning area the school files the subject under, and who marks it. Progress is then written against the school's own descriptors, in the words that will appear on the report.
Why it happens
A robotics kit works beautifully for two afternoons on the example that came in the box, and then it needs code nobody in the house can write. The kit sits on the shelf, and both the child and the parent quietly conclude that the child is not a coder.
How we fix it
The first two months run on whatever machine is already in the house, since a browser covers blocks and the first Python. Buy when the child asks for a specific thing the current setup cannot do, and can say what it is.
Why it happens
A video build produces a finished game in forty minutes, and a finished game feels exactly like understanding. Change one number the next day and the child cannot say which line to touch, because they never chose any of them.
How we fix it
Every session closes with one change the child makes alone: make the enemy twice as fast, then tell me which line you changed and why. That single question separates copying from knowing, and takes three minutes.
Why it happens
The real gates are reading fluency, two-handed typing and the patience to match brackets. A child still hunting for the letter K spends the whole session on the keyboard rather than on the idea, and concludes that programming is boring.
How we fix it
Reading and typing are checked in the first session, and the starting point follows the child instead of the age on the form. Moving up mid-term is normal and costs nothing; we watch for it rather than waiting for a term to end.
All five come from how children generally learn to program, and they sit here as the things we plan around. This page claims no results of its own: the work in Thailand has not started, and a record has to be earned before it can be shown.
A new brand cannot show you results. It can show you exactly how it works, and be held to that.
Every coding tutor opens a program they wrote themselves and walks through its worst bug before we take them on. Reading about programming and doing it look identical on a CV and nothing alike in that conversation.
You see the figure for your child's actual case before anyone arrives, including whether the sibling joining changes it. Travel within Bangkok is already inside it.
Tell us it is not working and the replacement costs nothing, with no case to argue first. In this subject a mismatch is almost always about pace, and it shows by the second or third session.
Sessions run on the laptop the child already uses, with the school's tasks open. Nothing is taught on a platform the child loses access to the moment the lessons stop.
After each session: what got built, which bug took longest, and one small thing to try. Written so you can tell how the hour went without knowing any Python.
When computing starts carrying marks, at IGCSE or IB Computer Science, the job changes and we hand over instead of stretching a children's programme over an examined one.
The subject attracts people who have read about programming and people who have done it. The interview is designed to tell them apart.
Screen sharing suits this subject unusually well, because the child keeps their hands on their own keyboard and the tutor watches rather than reaches. It is also the only way to reach a specialist who does not live in your district.
We match a tutor to the line your child lives on, because an hour lost on Sukhumvit at six o'clock is the difference between a lesson that happens on a school night and one that quietly stops happening. Districts covered: Watthana and Sathon; Bang Rak and Bang Kho Laem; Huai Khwang; Bang Na and Saphan Sung; Don Mueang. Beyond the city line: Nonthaburi, Samut Prakan, Pathum Thani.
Mostly about timing, equipment and whether it is too early or too late.
Even an abandoned project tells us more than a form does. Send the link, or just describe it, and we will say which starting point makes sense and why.
Ages are where most children sit, and every stage lists the thing to watch for rather than a birthday. Children arrive at these doors in their own order.
The idea comes first; the typing can wait.
Sample Project: A two-character story where the second character answers back, started and finished within three sessions.
Move to the next stage when: the child starts changing a project after it already works, rather than stopping the moment it works
A score, a way to lose, and an argument about fairness.
Sample Project: A game with a score, a losing condition and a restart that actually resets everything it should.
Move to the next stage when: the child argues about which rule to add next, which means they are designing rather than following
Spelling starts to matter, and so does patience.
Sample Project: A quiz that marks itself and keeps the best score in a file, so it survives being closed.
Move to the next stage when: the child fixes an error without being told which line to look at
Built to someone else's brief, and explained in writing.
Sample Project: A program built to a written brief, handed in with a short page saying what it does and what it cannot do.
Move to the next stage when: school computing starts carrying marks, at IGCSE ICT or IB Computer Science, and the tutoring changes with it
A child who reads early can begin text code at ten, and a child who reads late may be happier in blocks at twelve and lose nothing by it. The order of the stages matters; the birthdays attached to them do not. What we check in the first session is reading fluency and typing, because those two decide where a child can work comfortably today.