The campus roadmap

Where this is going πŸ—ΊοΈ

Most course sites show you a polished front and never admit what is missing. This page does the opposite: what exists, what is being built, and what is still only an idea. If something you want is in the third list, say so and it moves up.

Built and live

Two schools, open now βœ…

Everything here works today, free, with no account required.

πŸ¦€ The Rusty School

Learn Rust from zero

  • 28 lessons across five levels, starting before code begins
  • 9 workshop projects, ending with the web server that serves this site
  • 36 dojo puzzles in six belts, every one compiled before publishing
  • 5 quizzes, a glossary, cheat sheets, and a lab setup guide
  • Run any example in the page, via the official Rust Playground
Start Rust β†’
🐍 The Python School

Learn Python from zero

  • 68 lessons across seven levels, ending with your own AI assistant
  • 10 workshop projects, capstone included
  • 37 Snake Pit puzzles, plus the Insult Compiler for error messages
  • 7 quizzes, an 80-term glossary, 18 cheat sheets, XP and 21 achievements
  • Real CPython running in your browser. Your code never leaves your machine
  • The Jarvis Build: 12 guided chapters to your own AI assistant
Start Python β†’
πŸ”— One campus, one account Progress, quiz scores, milestones and achievements are shared. Lessons finished at one school count at the other, there is an achievement for learning both, and The Bridge lets you clear the same mission in either.

Recently landed

Shipped

The Bridge: a starship you have to repair πŸ––

You are the new Systems Officer aboard the UES Magnanimous, whose software is held together by optimism. Six seasons, 44 missions, every one a real coding problem wearing a uniform, and ARCHIE, the ship's computer, runs your code and tells you which objectives you actually met, with the input that broke it. Playable in Python or Rust, or both, because the two languages disagree about the interesting problems and that is worth playing. Ranks, a crew you meet as you go, an optional Red Alert timed mode, and a plaque with your name on it at the end.

Shipped

A quiz at the foot of every lesson

Two or three questions at the end of each lesson in both schools, 218 in total. They test the thing people actually get wrong rather than the vocabulary, and every wrong answer explains why it was tempting. Testing yourself beats re-reading by a wide margin, and it is the least glamorous finding in learning research.

Shipped

The Jarvis Build

The flagship project: build your own AI assistant from an empty folder in twelve guided chapters. It ends up remembering your conversations, running code you wrote, reading your own notes, and refusing to spend more than you allow. Every step is explained rather than assumed, and it costs less than a coffee in API charges to work through.

Shipped

A certificate when you finish

Complete every lesson in a school and the site prints your name on something you can hang on a wall. Drawn in your browser from your own progress, so no account and no upload are involved.

Shipped

An accessibility pass

Every level badge and label on both schools now meets the WCAG AA contrast standard in light and dark themes. One badge had been sitting at 1.78:1 in light mode, which is close to invisible. Progress toasts and code output are now announced to screen readers rather than only appearing.

Shipped

Search across both schools

Press / anywhere, or click Search in the menu. It looks through every lesson, project and puzzle in both schools at once. It runs entirely in your browser, so what you search for is nobody's business but yours.

Shipped

Optional accounts, at either school

Sign in with GitHub or Google and your progress follows you between devices and between both schools. No email is collected, and you can download or delete everything from your account page. Staying signed out still works exactly as well.

Shipped

Milestones and "what to do next"

Both schools now track a spine of named milestones, and every curriculum page suggests one concrete next action with a reason. The question "what should I do now?" is the one tutorials answer worst.

Shipped

The Python School

A whole second school: 68 lessons, generated and output-verified, which means every example was executed and its real output checked against the output the lesson promises.

Shipped

The impact counter

An anonymous count of lessons finished worldwide. No cookies, no identifiers, Do Not Track respected, and the counting code is public so you can audit the claim.

Being built

Next up πŸ”¨

Committed, in this order. Each one ships on its own rather than waiting for the others.

Next

Teaching guides and classroom mode

Notes so anybody can run a study group without preparing from scratch, then a class code and a dashboard so a teacher can follow along. The whole point of this project is teaching other people.

Not promised

Ideas, honestly labelled πŸ’­

Things worth doing that nobody has committed to. Listed so you can push one up the queue, not so it can look like a plan.

πŸ–₯️ More schools

The engine under both schools does not care about the subject. Likely next: a Terminal school (the shell, ssh, cron, a home server), then Web, then Data. A new school only opens when its first level is genuinely excellent.

🧭 Specialist tracks

Shorter courses after the core: Rust on the web with WebAssembly, game dev with Bevy, embedded Rust on a six-dollar microcontroller, or building a tiny programming language.

πŸ… Signature assignments

Publish a real crate. Land your first pull request on a real project. Port a slow Python script to Rust and publish your own honest benchmark. Things no other beginner course asks of you.

🌍 Translations

Every lesson is a separate file, which makes other languages very doable. Spanish and Portuguese first. This one needs volunteers more than it needs time.

πŸŽ₯ Video companions

Five minutes per lesson for people who learn better by watching, with the written lesson staying the canonical version.

🚨 "Explain this error"

A searchable page of the most common compiler errors and tracebacks in both languages, in plain English, because that is what beginners actually paste into a search engine at midnight.

πŸ’¬ Tell us what to build next This roadmap is a guess about what helps most, and guesses improve when somebody who is actually learning says otherwise. The most useful thing you can send is not a feature request: it is "this paragraph confused me". Confusing writing is a bug, and it gets fixed like one.

Suggest something on GitHub β†’ Read the source

πŸ“ The rules this roadmap follows
  • Beginner-first. Every page has to pass the test: would a total beginner understand this sentence?
  • Free and fast. The site is static, so it stays quick and costs nothing to run. Anything that would add a monthly bill gets flagged before it ships.
  • Nothing ships unverified. Rust examples are compiled and Python examples are executed, with their real output checked against what the lesson promises, before anything goes live.
  • The school is its own teaching material. The web server, the build scripts, the deploy pipeline: all readable, all in the open, all eventually rebuilt by you as an exercise.