How this series works

Updated

July 30, 2026

How this series works

30 Days of X is a series of independent volumes, not one course you must take as a bundle. Each volume (sub-book) is a self-contained, expert-ordered path of roughly thirty intensive study days. You choose which volume to follow and how to fit it into your life.

Relationship to 90 Days of X

This series is an intensive condensation of 90 Days of X. Each 30-day chapter combines approximately three original 90-day chapters into a single comprehensive session. The same expert-curated ordering and gate system is preserved, but compressed into four stages of ~7 days each.

Who this is for:

  • Learners who already have some programming/tech background and want faster pacing
  • People revisiting material they’ve partially seen before
  • Anyone who prefers intensive sprints over extended curricula

Who should use 90DaysOfX instead:

  • Complete beginners who need more time to absorb each concept
  • Learners who prefer a slower, more deliberate pace

Core ideas

  1. Volumes are separate. Finishing Go does not require NixOS (or any future volume), and the reverse is also true.
  2. One volume at a time is the normal mode. Studying two volumes in the same period is optional and entirely your decision—not a requirement of this resource.
  3. Expert order inside each volume. Day numbers are pacing guides; gates matter more than dates.
  4. Syllabus first. Narrative chapters are written against each volume’s syllabus contract.
  5. The series can grow. A successful volume → add another without rewriting existing ones.

What a volume contains

Piece Purpose
Overview Audience, baseline versions, “done” criteria
Syllabus 4 stages, 30 days, 4 gates, explicit out-of-scope
Chapters Mental model → examples → labs → gotchas

Stage structure (every volume)

Stage Days Role
Stage I 1–8 Foundations — core concepts and first gate
Stage II 9–15 Intermediate — deeper skills and second gate
Stage III 16–22 Applied — real-world usage and third gate
Stage IV 23–30 Mastery & capstone — production polish and final gate

Quality bar (every volume)

  • Prefer official docs over stale blogs when they conflict
  • Ship artifacts (repos, flakes, services), not only notes
  • End with a capstone that proves integration
  • No certification branding unless a volume deliberately adds exam prep later

Success for a single volume

You succeed when that volume’s overview checklist and capstone hold—regardless of whether you ever open another volume in the series.