How to pace a volume

Updated

July 30, 2026

How to pace a volume

There is no official morning/evening split and no required multi-volume day plan. This page is generic pacing advice for whatever single volume you are working on.

Intensive session shape

Each 30-day chapter combines ~3 original topics. Plan longer sessions than you would for a single-topic day. A useful internal split:

Slice	Rough share	Purpose
Concept	~25–35%	Mental models, docs, examples across all topics in the chapter
Hands-on	~45–55%	Code, rebuilds, exercises — work through all labs
Review	~15–20%	Refactor, commit, write gotchas, connect the topics

Expect 2–4 hours per day depending on your background and the volume. Some days (especially gate days) may take longer.

Expert pacing rules (any volume)

Protect gates. If a stage gate fails, stay there before advancing day numbers.
Small commits. Prefer many small green checkpoints over one giant untested change.
Stop on dangerous breakage. For systems work (e.g. NixOS), roll back and leave a note rather than “fixing” while exhausted.
Weekly review (30–60 min). Refactor, delete dead experiments, write a few gotchas in your own words.
One volume focus. If you also study something else, that is your schedule—not this book’s curriculum design.

Weekly rhythm (suggested for ~5 days/week)

Week	Days	Focus
Week 1	1–8	Stage I — Foundations + Gate I
Week 2	9–15	Stage II — Intermediate + Gate II
Week 3	16–22	Stage III — Applied + Gate III
Week 4	23–30	Stage IV — Mastery & Capstone + Gate IV

Doing 2 days per calendar day gets you done in ~2 weeks. Doing 1 day per weekday takes ~6 weeks. Both are fine.

Environment

Requirements are per volume (see that volume’s overview). Example:

Go volume: Go 1.26.x, editor with gopls, ability to run tests (later -race).
NixOS volume: disposable VM or spare machine, disk for /nix/store, flakes-capable Nix.

Calendar honesty

“30 days” names a shape, not a deadline. Stretching a volume over more calendar time is normal and often better.