Build phases
One meaningful runtime boundary at a time.
C / BUILD THE RUNTIME
Stop collecting concepts. Build the machinery, break it on purpose, measure what happened, and leave with seven working systems you can explain from bytes to behavior.
$ node lab.js --inspect-runtime
THE LAB CONTRACT
Every lab gives you enough scaffolding to keep moving and enough open space to make the engineering decisions yourself.
One meaningful runtime boundary at a time.
Prove behavior before the next abstraction.
Get unstuck without losing the discovery.
Recognize failure shapes before fixing them.
Compare against observable evidence.
Judge the system, not just the happy path.
THE COMPLETE BUILD CATALOG
Start anywhere. Each lab is a complete build with its own phase plan, checkpoints, observable outputs, failure paths, and final evidence.
Observe child processes, stdio, signals, memory, CPU, event loop delay, active handles, warnings, crashes, and runtime evidence.
Create an append-only log database with record checksums, indexed reads, crash recovery, tombstones, compaction, and benchmarks.
Build an NDJSON pipeline, compare whole-file and streaming paths, expose backpressure, add gzip and aborts, then prove the tradeoffs.
Trace import and require lookup, package exports, conditions, interop hazards, caches, cycles, symlinks, and resolver decisions.
Scan directories, hash files, persist cache state, normalize uncertain filesystem events, debounce rebuilds, and verify every result.
Build a local job orchestrator with dependencies, concurrency limits, retries, timeouts, cancellation, durable progress, and reports.
Design a byte-level protocol and TCP gateway with stateful parsing, malformed-frame defenses, bounded sinks, metrics, load, and reports.
OWN THE WHOLE WORKSHOP
NodeBook Pro combines the complete Digital Bundle with every Runtime Lab, future updates, PDFs, and EPUB editions.