How the Academy teaches
Wasteology Academy borrows its teaching philosophy from the very thing its first track is about: learn by doing, and treat "done" as something you prove, not something you claim. Every module is built the same way, and every track will be too.
Local-first, then cloud
Just like the ADW loop itself starts on a developer's own Claude Code subscription before anything touches metered cloud infrastructure, the Academy starts local: your progress lives in your browser from the moment you open your first lesson, no sign-in required.
The ADW Track's own content teaches "local-first, then scale to the cloud" as a design principle. The Academy platform you're using to learn it works the same way — try it locally, upgrade to the shared/cloud version when you're ready. That's not a coincidence.
Every module has three parts
Whatever the track, every module follows the same three-part shape:
- Concept — a grounded explainer of the idea, usually with a diagram or a short video. No hand-waving: claims are tied to the real mechanism, and anything illustrative or "marketing" framing is called out as such rather than presented as fact.
- Hands-on lab — you actually run the commands, write the spec, or trigger the workflow. Reading about the ADW loop doesn't teach you the ADW loop; running it does.
- Knowledge check — a short quiz that gates progression. It's not a test for its own sake — it's a checkpoint that you can explain why, not just that.
The ADW loop refuses to let unverified work reach a PR — an independent maker-checker gate and an evidence artifact (RESULTS.md, a recorded walkthrough) have to exist before anything is called done. The Academy applies the same standard to learning: a lesson isn't "done" because you scrolled past it, it's done when you've done the lab and passed the check.
Progress tracking: local-first, upgrades when you're signed in
Your progress — which lessons you've started or completed, your quiz scores — is tracked as you go:
- Out of the box, progress is saved in your browser's
localStorage. This works immediately, works offline, and requires no account. It's tied to that one browser, though — switch devices and you start fresh. - Signed in via Entra (company SSO), the same actions are also recorded by the Academy's backend, so your progress follows you across devices and persists even if you clear your browser data.
The site is built to degrade gracefully in the other direction too: if the
backend is ever unreachable, lessons and quizzes keep working against
localStorage alone. Content should never be blocked on infrastructure. See
Tracks, progress & certificates for what
this looks like from your side, and the architecture notes on the LMS backend
for the implementation.
Certificates on completion
Finish every module in a track — including its capstone, if it has one — and you get a certificate for that track. It's the Academy's answer to "how do I know I actually learned this, and how does my manager know too": a concrete, recorded artifact tied to your identity, not a self-assessment.
This learning model isn't specific to ADW. Concept → lab → check → progress → certificate is the shape every future Academy track will use, which is what lets new tracks be added as pure content — no changes to how the platform teaches.