knaxuslearn · build · ship

Roadmaps

Each roadmap is built around one project you finish at the end, with a checkable “done when” at every step. They are in beta while we tighten the hours and entry levels.

why these are different

Every roadmap ends with something you built

A list of topics can keep you reading for months. These roadmaps give you a project and a finish line, so you always know what to build next and when you are done.

A typical topic mapA Knaxus roadmap

Starts from a list of topics to cover.

Starts from one project with a real scenario and numbers.

You are done when you have read everything.

You are done when a check a stranger can run passes.

No time estimate, so the end never comes.

128 hours over 16 weeks, paced to your week.

Every topic gets the same weight.

Only what the project needs is on the core path.

Ends with a ticked list.

Ends with a repo, a write-up and a benchmark you can show.

How it works for you

  1. One project

    You build a single real system from the first week to the last. Every phase adds a working piece to it.

  2. A check you can run

    Each phase ends with a "done when" that a stranger could verify, often with a planted fault your tests must catch.

  3. Fixed hours

    The core path is 128 hours over 16 weeks, with pacing for 8, 12 or 16 hours a week.

  4. Proof at the end

    A worked reference shows what a finished checkpoint looks like. Each roadmap also has a version you can run on a real problem at work.

Foundations

Programming Languages

Data, AI and web

Electronics