Ages 5-7
Coding for Ages 5-7 in Frisco, TX - Before They Can Read
A five-year-old can learn sequencing, loops and cause-and-effect long before they can read a line of code. Junior is built so nothing depends on reading or typing speed.
How it works
Junior is a weekly one-hour class, not drop-in - a small group at the same time each week, so the youngest ninjas get routine and the same faces.
What they actually do
Visual coding in ScratchJr and codeSpark, unplugged logic games away from screens, and hands-on robotics and simple circuits. Roughly half of each term is off-screen.
When they move up
Most move into Create around age 8, or when reading is comfortable. There is no test - the senseis know when a ninja is ready.
The full pathway
Ten levels, and what happens in each
10 levels and 30 named projects, from sequencing to their first robotics. Every level has a concept behind it, and a sensei checks a ninja can explain it before they move on.
Algorithms & Sequencing
- Dance Party
- Sound Farm
- My World
Plus 3 codeSpark puzzle sets on the same idea.
What a sensei checks
- Ninja can explain what a sequence means (steps in order)
- Ninja added at least 2 motion blocks to a sprite
- Ninja pressed the green flag and their character moved
- Ninja can say what their character did first, second, third
- Ninja added a sound block to their project
- Ninja's sequence includes at least motion + sound
- Ninja can explain why the order of blocks matters
- Ninja ran their project and it did what they expected
- Ninja created a scene with at least 2 sprites
- Each sprite has its own sequence of blocks
- Ninja can point to the start block and explain what it does
- Ninja can describe their world story in order
Debugging
- Bump You're It!
- Seasons
- Ocean of Code
Plus 3 codeSpark puzzle sets on the same idea.
What a sensei checks
- Ninja can say what a bug is in their own words
- Ninja found at least one mistake and fixed it
- Ninja's character bumps into another object correctly
- Ninja did not give up when something didn't work first try
- Ninja changed backgrounds in sequence (at least 2 seasons)
- Ninja can explain what was wrong before they fixed it
- Ninja tested their project after each fix
- Ninja can describe the bug they found
- Ninja's ocean scene has moving sprites
- Ninja fixed at least one block that was in the wrong order
- Ninja can walk through their code block by block
- Ninja tested their project and it runs without stopping unexpectedly
Loops
- Repeat Repeat Repeat
- Dribble Dribble
- Close and Far
Plus 3 codeSpark puzzle sets on the same idea.
What a sensei checks
- Ninja can explain what a loop does in their own words
- Ninja used at least one repeat/loop block in their project
- Ninja can show the difference with and without a loop
- Ninja's character repeats an action correctly
- Ninja's character bounces or dribbles using a loop
- Ninja can explain why loops save time (vs. copying blocks)
- Ninja changed the number of repeats and saw the difference
- Ninja can identify the loop in their project
- Ninja used loops to move a sprite back and forth
- Ninja can explain what happens when a loop never stops (forever loop)
- Ninja's character grows/shrinks or moves in a repeated pattern
- Ninja can point to where the loop starts and ends
Decomposition
- Catch Me If You Can!
- Custom Characters
- Stage of Code
Plus 3 codeSpark puzzle sets on the same idea.
What a sensei checks
- Ninja broke the project into smaller parts before building
- Ninja can name at least 2 parts of their project
- Ninja's character moves and can be caught (touches another sprite)
- Ninja can explain how they planned their project
- Ninja drew or modified at least one character in the paint editor
- Ninja can explain the steps used to make their character
- Ninja's custom character appears in a working project
- Ninja can describe what makes their character unique
- Ninja built a scene by decomposing it into background + sprites
- Ninja added code to both background and at least one sprite
- Ninja can list the separate parts of their project
- Ninja's scene tells a mini-story with a beginning, middle and end
Advanced Sequencing
- My House
- Safari Adventure
- Where Am I?
Plus 3 codeSpark puzzle sets on the same idea.
What a sensei checks
- Ninja built a house scene with multiple sprites and a background
- Ninja's sequence is longer than 4 blocks for at least one sprite
- Ninja can walk through their sequence step by step
- Ninja's project runs from start to finish without stopping
- Ninja's project has at least 3 different animals/sprites moving
- Each sprite has its own independent sequence
- Ninja can explain why exact order matters in a long sequence
- Ninja's project tells a story from beginning to end
- Ninja used directional movement with precision
- Ninja's sprite ends up in the right location
- Ninja can explain what would happen if one step were in the wrong order
- Ninja's project runs correctly from the start block
Events
- Say It!
- School Story
- Hot Potato
Plus 3 codeSpark puzzle sets on the same idea.
What a sensei checks
- Ninja added a speech/say block to a character
- Ninja's character speaks when triggered by an event
- Ninja can explain what an event is (something that triggers code)
- Ninja's character only talks when the event happens - not all the time
- Ninja created a multi-character story triggered by events
- At least 2 characters respond to different events
- Ninja can explain the difference between a start block and a message trigger
- Ninja's story has a clear beginning event that kicks everything off
- Ninja's project passes a message between sprites using send/receive
- Ninja can explain how one sprite tells another to do something
- Ninja's project has an event that changes what happens on screen
- Ninja tested the event by triggering it manually
Conditionals
- Enter the Castle
- Space Station
- Turn the Page
Plus 3 codeSpark puzzle sets on the same idea.
What a sensei checks
- Ninja's project has a condition (something happens IF character reaches a place)
- Ninja can explain IF/THEN in their own words
- Ninja's character does one thing in one situation and something different in another
- Ninja tested both outcomes of their condition
- Ninja used a collision or touch condition
- Ninja can describe the condition: IF this happens THEN that happens
- Multiple sprites run at the same time (synchronization)
- Ninja can point out which parts of their project run simultaneously
- Ninja's project changes pages/scenes based on a condition or event
- Ninja can explain how synchronization works (things at the same time)
- Ninja's project has at least 2 things happening simultaneously
- Ninja tested the page-change trigger
Stacks & Queues
- One of These Things
- Choose Your Own Adventure
- Flying Fish
Plus 3 codeSpark puzzle sets on the same idea.
What a sensei checks
- Ninja can explain what a stack is (last in, first out) in simple terms
- Ninja's project has sprites that appear or disappear in stacked order
- Ninja tested that the order is correct
- Ninja can connect the stack concept to something in real life
- Ninja built a branching story with at least 2 different paths
- Ninja can explain how the queue concept applies (things happen in a line)
- Ninja tested both branches of their story
- Ninja's adventure has a clear end to each path
- Ninja's fish moves in a synchronized pattern with another element
- Ninja can explain the difference between a stack and a queue
- Ninja's project has multiple sprites working in coordinated order
- Ninja can trace the order in which things happen in their project
Pair Programming
- Keep Away
- Super Wheelie
- Crossy Road
Plus 3 codeSpark puzzle sets on the same idea.
What a sensei checks
- Ninja successfully played the Navigator role (gave instructions only, didn't touch)
- Ninja gave clear, specific directions to their partner
- Ninja can explain the difference between Driver and Navigator
- Ninja's partner was able to follow their instructions
- Ninja stayed in their role throughout (Navigator or Driver)
- Ninja communicated respectfully with their partner
- Project was completed collaboratively - both contributed
- Ninja can explain one thing they learned from working with a partner
- Ninja has now experienced both Driver and Navigator roles
- Ninja can explain which role they prefer and why
- Ninja's Crossy Road project has a moving character that crosses the screen
- Ninja can describe one challenge of pair programming and how they solved it
Game Maker
- Underwater Treasures
- My Story
- My Game
Plus 3 codeSpark puzzle sets on the same idea.
What a sensei checks
- Ninja's project has a game goal (collect something, avoid something)
- Ninja can explain the rules of their underwater game
- Ninja's game has a win or lose condition
- Ninja tested the game and it works as intended
- Ninja created an original story using all learned concepts
- Ninja's story has events, loops, and at least one conditional
- Ninja can walk through their story explaining each part
- Ninja's project runs from beginning to end without errors
- Ninja designed and built an original game from scratch
- Ninja can state the rules of their game clearly
- Ninja's game has a start, a challenge, and a way to win or lose
- Ninja playtested their game and made at least one improvement
- Ninja can explain which coding concepts they used and where
“Since joining Code Ninja Frisco West, he’s become comfortable and confident with using the keyboard and mouse.”
School breaks
Camps for younger ninjas, too
During the school year it is a class a week. School breaks are full days, 9am to 3pm, with a finished project by the end.
Every camp and the next dates
Ages 6+From our parent guides
What Age Should Kids Start Coding?
Kids can start at 5 with tools that need no reading. Here is what suits each age, and how to tell they are ready.
Before you ask
Common questions
My child cannot read yet. Is that a problem?
No - that is the point of Junior. The whole curriculum is visual.
How long is a class?
One hour, once a week.
Is it all screen time?
No. A significant part of each term is unplugged - logic puzzles, circuits and robotics you can hold.
What if we miss a week?
Nothing is missed. A ninja picks up at the point they were at rather than wherever a class has reached.
What happens when they turn 8?
They move up to Create, which is the same idea with real code in place of the visual blocks.
See it for yourself
A free session is the honest way to judge whether this suits your child.
Open Monday to Thursday 4-7pm and Saturday 10am-2pm.