Docs · How labs work
How labs are graded
Most certificates prove you watched the videos. Ours prove your code runs — AI-assisted to build, held-out to verify.
The pass rule
Every lab is auto-graded on running code: it passes only when both companion scripts exit cleanly on your solution — not quizzes, not completion.
both lab scripts pass on your code — i.e.run_lab.sh and run_tests.sh both exit 0 on your solution. Both scripts pass — this lab counts.That's the whole bar: not a multiple-choice quiz, not a “mark complete” button — your code has to actually run and pass. It's the same signal a job interview cares about.
Two kinds of lab
Guided lab
AI-assisted, with Claude Code, hints, and a per-step answer reveal — so you can't get stuck. Auto-graded on running code. This is the standard lab — you can’t get stuck, and it’s still graded on running code.
Verified checkpoint
ComingA held-out checkpoint is coming: a held-out problem, server-graded with no AI pair-programmer, certifying a single named skill. No AI pair-programmer, a problem the course didn’t walk you through — it certifies that you can apply a skill unaided. Until it ships, no profile shows a Verified badge.
Working a lab
- A real VS Code workspace opens in your browser — no local setup, no Docker.
- Each lab has a few TODOs marked in the code; implement them, then run the lab.
- Run early and often — the loop is fast. Stuck? Claude Code is in the terminal, and Guided labs have a per-step answer reveal.
- The workspace persists for 24 hours, so you can come back to it.
Every passed lab becomes a signed node on your skill graph — a recruiter-auditable record of the labs you actually passed.
Was this page useful?