Children should build with technology.
Games, circuits, simulations, and robot logic turn a device from a stream of content into material for construction.
Our Method
Build something small enough to finish and rich enough to think about.
School of Code teaches ideas through visible systems. The project is not a reward after the theory; it is where the theory becomes testable.
A program is a text.
It has structure, sequence, intention, revision, and a reader: the computer. Code says something precise enough to run.
The student is an author.
Students should make consequential choices, not only reproduce the instructor's finished answer.
Knowledge is a web.
Coordinates connect to movement, movement to collision, collision to conditions, and conditions to state. Useful ideas keep meeting.
Theory is the skeleton.
A project can look lively, but theory gives it a structure the student can understand, repair, and reuse.
Stories give ideas weight.
A strange mission provides a reason for a coordinate, condition, or sensor rule to matter right now.
Mistakes are data.
A bug reveals a difference between the intended system and the actual one. That difference is a clue, not a verdict.
Structure and anarchy.
The lesson protects the learning goal. Within it, students can change rules, artwork, routes, constraints, and implementation choices.
Meaningful difficulty.
A task should resist automatic completion without becoming so large that no version can be finished and explained.
Small groups matter.
The instructor needs to see the actual project, not only whether the editor looks busy.
Demonstration completes the cycle.
A student shows the system, names a bug, identifies a choice, and explains the evidence behind a repair.
Class and Lab have different jobs.
The class gives the idea. The lab gives the idea a life through modification, testing, rebuilding, and invention.
The goal is not merely to make code run. It is to understand enough of the system to change it on purpose.
Teaching model
A route from curriculum to visible work.
- Program
- Topic
- Lesson
- Guided Project
- Lab Project
- Parent Explanation
- Gallery / Blog
School of Code laws
Short enough to remember while debugging.
- Build a small working version first.
- Predict before pressing run.
- Reset to a known state.
- Change one cause when testing.
- A bug is a clue.
- Name the idea underneath the joke.
- Make one rule your own.
- Finish by demonstrating and explaining.
Public curriculum
See the method operating, not only described.
The topic, lesson, and project libraries expose goals, theory kernels, checkpoints, common mistakes, challenge levels, and parent explanations.