Coding for kids in the Philippines at Eduline takes children aged 7 to 16 from Scratch blocks to typed Python, one tutor with one learner. It sits outside DepEd and off the report card, so the test is simple and visible: breaking a problem into steps small enough for a computer to follow, then finding exactly where it went wrong.
210+
Active tutors
500+
Learners taught
55+
Cities
210+
Active tutors
500+
Learners taught
55+
Cities
What is
One-to-one programming lessons for children roughly between seven and sixteen, starting with block-based tools and moving to written code the week the young coder's reading and typing are ready for it. Each session ends with something that runs, because a child who has not seen their own work do something has no reason to come back.
Key Points
The whole lesson already happens on a screen, which changes what in-person actually means for coding
The work already lives on a screen, so a shared screen loses nothing. The tutor can see the code, take control to point at a line, and hand it straight back. For this subject, remote is the natural setting.
Better for younger children, who need somebody to notice they have stopped and are staring. Also better where the household has one computer and it is easier for the tutor to come to it. For the youngest children, the ninety minutes rarely happens in one push: it breaks into shorter rounds of actual coding time, each followed by a real pause, because a seven-year-old's attention for this kind of screen work gives out long before the visit is over.
Measured by what the child makes
However small. A child who has spent an hour on theory and has nothing working has learned that coding is boring, which is the opposite of the point.
You see exactly what each lesson contains: the concept, the project and the bug fixed along the way. That is how the value of each hour is judged, and it is visible from week one.
Programming tools change every few years. Breaking a big problem into small steps, testing each one and fixing what breaks is the habit these lessons build, and it serves a child in every field they later choose.
A ten-year-old who reads well may be ready for written code; a thirteen-year-old who does not may not be. Moving too early to text code is the fastest way to lose a child who was enjoying it.
Motivation is the whole engine here, and it does not survive contact with somebody else's idea of a good exercise. The tutor steers the method, and the learner steers the subject. The learner chooses the tutor as freely: a new coding tutor is free whenever you ask, and the project in progress carries over.
What a session costs depends on the child's level, the mode, and the area, so this page shows a from-rate, and the exact figure follows the level. Asking for the actual figure does not commit anyone to booking a session.
Reading and typing set the pace far more than age does
| Aspect | Roughly 7 to 9 Blocks, and the idea of a sequence | Roughly 10 to 12 Logic, and projects that take more than one sitting | Roughly 13 to 16 Real code, in a real language | Any age, already started Stuck, or self-taught and patchy |
|---|---|---|---|---|
| Description | Drag-and-drop programming, where the instructions are physical things that snap together. No typing and no syntax, so the only thing being learned is the actual idea: that a computer does exactly what it is told, in order, and nothing else. | Still often block-based, but the projects get big enough that planning starts to matter and a child cannot hold the whole thing in their head. This is where the transferable part actually appears: breaking something large into parts. | Python or JavaScript, written as text, with all the unforgiving punctuation that implies. The step up is less about difficulty than about tolerance: a misplaced colon breaks everything, and learning to be unbothered by that is most of the work. | Already fluent at following a tutorial: copies the code, watches it run, and understands each line. Sits down to an empty editor and freezes. This is the most common starting point here. Every tutorial already decided what to build and where to begin; the one skill never practiced is making that decision alone. |
| Subjects | Scratch and block-based toolsSequence, loops and eventsSimple animationsSimple games | Conditionals and variablesMulti-part projectsIntroduction to typed codeReading someone else's program | Python or JavaScriptFunctions and data structuresWorking with files and simple dataA project the learner chose | Filling in what the tutorials skippedStarting from a blank fileDebugging as a methodFinishing an abandoned project |
| Focus Areas |
|
|
|
|
The tools are the visible part; the list below is what is really being built
The language matters far less than most people expect. A young coder who understands loops and conditions in Scratch already has the idea; moving that into Python is a translation exercise.
Module 01
That a computer does what it is told, exactly, in order, and has no idea what you meant. Obvious to adults, genuinely new to a child, and the foundation of everything after it.
Module 02
Repeating work, and making decisions. The two ideas that turn a list of instructions into a program, and the point at which most children first build something genuinely their own.
Module 03
The part that is worth the money. Taking something too big to hold in your head and splitting it until each piece is small enough to be obvious: a skill that has nothing to do with computers.
Module 04
Finding out where you were wrong, without taking it personally. Most of programming is this, and a child who becomes comfortable with it has gained something that outlasts every language they will use.
Module 05
Something the child picked, carried through to a finished state. Choosing the project is part of the lesson, and abandoning three before finishing one is completely normal.
Module 06
Files, folders, saving, typing without hunting. Quietly one of the most useful outcomes here, and something a generation raised on phones frequently has never been taught.
The natural home for this subject. Work already happens on a screen, the tutor sees the same code the learner sees, and projects are saved so the next session picks up where the last one stopped.
Timezone: Philippine Standard Time (UTC+8)
A tutor sits beside the child at one shared screen, positioned to catch the moment focus drifts and a game opens in another tab. Send your city and the coding tutor nearest you is matched. A home session runs at least an hour and a half, long enough to reopen last week's project before anything new gets built.
Four kinds of learner, and the start that suits each
Already modifying games, building in Roblox or Minecraft, asking how something works. The easiest case: the motivation is there and the lesson only has to supply method.
Recommended:
Enjoys logic problems, patterns, taking things apart. Coding gives that instinct something to chew on that also produces a result, which is rarer than it sounds.
Recommended:
Can follow a tutorial and cannot start one. The missing piece is almost never syntax; it is having never had to decide what to build first.
Recommended:
Interest is what makes coding stick, so a curious but unsure child starts with a short run built around a game or story they already love. The review at the end of it shows plainly whether the spark has caught.
Recommended:
One tutor and one learner, priced by the hour. What is shown above is where coding starts; a few things move it from there.
From
₱400 / hour
| Home visit, Metro Manila | ₱550 / hour |
| Online | ₱400 / hour |
| Home visit, provincial areas | ₱400 / hour |
Per hour, one tutor with one learner. Home visits run at least 1.5 hours. Packages: 12 hours at 5% off, 24 hours at 10% off.
The figure above is priced for the youngest stage on this page, roughly seven to nine years old and working in blocks. A teenager on the same subject, already writing real code in junior or senior high, sits on a higher rung of the ladder, priced the same way any other program is at that age. From there, a tutor coming to a home in Metro Manila costs more per hour than an online session, and outside Metro Manila a home visit drops back to the online rate. A coding project is rarely finished in a single sitting, so a learner booked in weekly across a school term usually takes the twelve-hour or twenty-four-hour block and takes the discount.
Including the questions we get asked warily
The habit it builds is visible in every lesson: a big task chopped into pieces small enough to attempt, each piece tried, checked, and fixed when it breaks. Watch for it at home, in a child who stays with a hard problem longer. The report card itself stays the school's measure.
Other questions
Tell us the age, anything they have already tried on their own (Scratch, a tutorial, a half-finished game), and what computer the household has to work with. A real person reads it and writes back with the best starting point for this coder, plus the rate for their level and a tutor to meet.