They build.
Your child works in a pair on a real program. One builds while the other predicts and reviews, then they switch.
A coach notices.
Coaches name what your child just did well, in the moment: “That's teamwork. You made room for your partner's idea.” Classes are limited to 10 students.
Progress you can see.
Your child moves up with real project work and real character evidence. You get a simple email on what your child learned and how they're progressing.
It's okay to be new at this. Everyone starts at the beginning, and your child is taken seriously here.
Hours of games and feeds, and nothing built?
Screens are not the problem. Hours of games and feeds that entertain and build nothing are, at an age when kids can make real things.
A class can feel too young for a middle schooler, and a description rarely shows whether your child will respect it. What matters is real work your child is taken seriously for.
Kids shouldn't have to choose between what they love and who they can become.
The plan
Start your membership.
Watch your child try, build, and test.
See skills and character grow, class after class.
- No prior experience is needed, and your child does not bring equipment.
- Parents may observe where operationally appropriate.
- You get a simple email on what your child learned and how they're progressing.
What a class looks like
No experience needed, and your child does not bring equipment.
Plan and build
Put the steps in order with a partner so the program reaches its goal.
Predict and run
Say what the program will do and why, then run it and compare.
Review and fix
Trace it one step at a time, find where it differs, and fix it with a coach asking questions, not giving the answer.
Explain
Show or tell why the program did what it did.
What your child learns in Code Navigators
Every skill is practiced and shown in class, not memorized.
Put steps in order
Plan 3 to 5 steps so a program reaches its goal, with cards on paper and with blocks on a screen.
Explain why a program did what it did
Point to the instruction that caused a result.
Run a program and say what happened
Start it, watch it, and report what it did.
Predict before running
Say what the program will do and why, then run it and compare.
Work well with a partner
Contribute to the plan, make room for others, and stay respectful.
Use a loop instead of copying steps
Say “repeat 5 times” once instead of writing the same step five times.
Spot patterns that repeat
Notice a pattern that repeats and build it with a loop.
Check the result
Say whether the result matched what was expected, and point to what looked different.
Find and fix a bug
Locate and fix a mistake in a short program with little or no coach help.
Try again before asking for help
Try a second approach first, and explain what was tried.
No typing tests, spelling, memorized definitions, timed exams, or fixed quiz scores. Your child does not need to type fast or already know how to code. Kids who prefer to show, draw, or talk instead of write can do that.
What parents notice
Before
Hours of games and feeds. Capable, but not sure it is worth the effort.
After
From a kid who consumes, to a builder who works well with a partner and checks their own work.
Class details
Grades: 6th-8th
Up to 10 students
Thursday · 7:00 PM – 8:00 PM
Kansas City / Northland · Kansas City
Frequently asked questions
Older students work in pairs on real programs and review each other's work. It is real work, and they are taken seriously.
Quiet engagement counts. Your child can show, draw, or talk through their work, and coaches notice contributions in the moment.
It is screen time that builds something. Your child plans, predicts, runs, and explains a program.
Your middle schooler can spend another year consuming, or start building.
Start Your Membership