Docs · Getting started

Day-zero walkthrough

Five steps from your first login to your first finished lab — real code, running on our cloud, with nothing to install. Roughly 90 minutes end-to-end if you don't pause.

Step 1

Pick a discipline

A discipline is a career track — for example, GenAI Engineering or AI Security Engineering. Each one bundles 5–11 courses and roughly 95–280 chapters of focused work.

Open the Disciplines page to browse what's available.

The Disciplines page — a grid of GenAI engineering discipline cards, each with its course and goal counts — The Disciplines page · click any card to see its courses.

Step 2

Enroll in a course

Each discipline has multiple courses, sequenced for compounding. You'll see chapter previews before you commit, and every discipline unlocks a set of free preview lessons so you can scope-check before subscribing.

Once you're enrolled, the course shows up in your Progress dashboard and on the home page as a “Continue” card.

Step 3

Open your first lesson

Open any lesson (a chapter is just a set of them). A lesson teaches one goal — its reading, quiz, and lab all point at that single outcome. Every lesson has the same four steps: Read → Quiz → Lab → Capabilities — read, quiz, build, then see what it proves. Jump between them freely; each chapter also has an audio overview. Progress saves as you go.

A lesson page — its title, its one-line outcome, and the Read → Quiz → Lab → Capabilities stepper — A lesson page — the same layout in every course, with the course path in the left rail.

Step 4

Run your first lab

Open the lesson's Lab step. After ~30 seconds, a real VS Code workspace opens in your browser. Each lab has a few TODOs marked clearly in the code. Implement them, run the lab, and iterate until both scripts pass on your code.

No local setup. Tests run on GenBodha's cloud — no Docker, no dependency hell. Your live session pauses after 30 minutes idle and runs up to 4 hours at a stretch, and your saved files are kept for months of inactivity — reopen before then to pick up where you left off.

A lab's README preview — Lab Context, Business Value, a Source Files diagram, and a table mapping each TODO to a function and its rationale — Every lab opens with a brief — context, business value, the files, and a map of each TODO.

The lab workspace — file tree on the left, the starter file with its TODOs in the editor — A real VS Code workspace · the TODOs are marked right in the code.

Claude Code running in the workspace terminal, asked how to better understand a TODO — Stuck? Claude Code is built into the terminal — ask it how to approach a TODO.

The lab terminal showing run_lab.sh output ending in 'Application ran successfully!' — Run the lab — both scripts pass on your code, and the lab counts.

Step 5

Track progress

Your progress dashboard shows everything: labs passed, coverage, and your current credential tier — plus where you left off, your disciplines, and Practice Reps. Use it to see what to do next and how far you've come.

Your dashboard — labs-passed / coverage / tier stats, a card showing your next lesson, your disciplines, the Frontier, credentials, and Practice Reps — Your dashboard · your next lesson, plus disciplines, credentials, and Practice Reps.

Was this page useful?