Core syntax
Core syntax is revisited at pace and under time pressure, so recall becomes automatic rather than effortful.
Python for Kids · Class 10 · Module 1 of 9
Python Readiness Sprint
Board year. Time to make every habit count.
8 sessionsSessions 1–8
4 weeksTypical pace
Intermediate to AppliedLevel
Class 10Python & Coding
The big idea
A rapid consolidation of core Python at full speed, plus the two habits that define working developers: version control for tracking change, and code review for catching what the author cannot see.
Why it matters
Class 10 is the launchpad into serious computing study. Confidence in the fundamentals leaves room to think about design instead of syntax.
Unpacked
What you will actually learn
Three core ideas, each taught with worked examples and then practised until it feels obvious.
Git concepts
Git concepts — commit, branch, history — give a project an undo button that spans months, and a record of why each change happened.
Code review
Code review means reading someone else’s code and asking useful questions. Reviewing teaches at least as much as being reviewed.
Did you know?
Git was written by Linus Torvalds in about ten days in 2005 because no existing tool could handle the Linux kernel’s scale.
Common mix-up
“Commit when the feature is finished.” Small, frequent commits with honest messages are far more useful when something breaks.
Session by session
Your 8-session journey
Sessions 1–8 of the 72-session year, at two one-hour sessions per week.
- 1
Warm-up and big picture
Where this module fits, what you will build, and a hands-on starter that gets everyone curious about core syntax.
- 2
Core syntax
Guided teaching on core syntax, worked through together with the teacher.
- 3
Core syntax — practice lab
Independent practice, small challenges and one deliberate mistake to diagnose.
- 4
Git concepts
Guided teaching on git concepts, building directly on the previous two sessions.
- 5
Git concepts — practice lab
Applied tasks that combine core syntax and git concepts in one piece of work.
- 6
Code review
Code review introduced and practised, completing the toolkit needed for the project.
- 7
Project build
Guided build session for the module project: Refactored multi-file utility.
- 8
Test, present and reflect
Finish, test against the checklist, present the work and explain the decisions behind it.
Project lab
Refactored multi-file utility
Every module ends with something the student built themselves and can demonstrate. This is the piece that goes into their portfolio and gets explained out loud at the end of session 8.
Try this at home
Refactor an old multi-file project with commits at every step, then read your own history back and see whether it tells a clear story.
It is finished when
- It works from start to finish without breaking
- You can explain every part of it in your own words
- You tested it and improved at least one thing afterwards
- Someone else used or understood it without your help
By the end of this module
Students finishing Module 1 can:
- Explain and use core syntax without prompting
- Explain and use git concepts without prompting
- Explain and use code review without prompting
- Build and finish refactored multi-file utility
- Test your own work and correct what you find
- Talk an adult through what you made and why
Word bank
The vocabulary introduced here, in plain language:
- version control
- A system that tracks changes to code over time.
- commit
- A saved snapshot of a project with a message.
- code review
- Structured reading of code by another person.
Module challenge
Think you have got this?
0 XPLevel 1 · Curious Beginner
6 quick questions drawn from this module — vocabulary, the project you build, and a myth-or-fact round. Every wrong answer explains itself, so a mistake still teaches you something.
Your child's free trial is one message away.
Tell us your child’s class and what they enjoy. We will suggest the closest program fit—no pressure and no upfront payment.