Topics / runtimes
Languages and runtimes
The work a language runtime does on your behalf: scheduling goroutines, collecting garbage, and running portable bytecode safely and fast.
- What V8 does with your JavaScript, 9 levels · 43 min · Idea to Machine
- Go concurrency, from go keyword to OS thread, 8 levels · 45 min · Idea to Machine
- Go’s garbage collector, from GOGC to the cache line, 8 levels · 45 min · Idea to Silicon
- Rust ownership: the checks and the machine, 8 levels · 42 min · Idea to Machine
- Zig comptime: the compiler runs your code, 8 levels · 40 min · Idea to Machine
- WebAssembly, top to bottom, 10 levels · 40 min · Idea to Machine
The path
Read in this order and each dive leans on the ones before it. Every dive also stands on its own.
- 01
What V8 does with your JavaScript
One distance function, four execution tiers, and an assumption that breaks. Step through real bytecode, build hidden classes, feed an inline cache, and follow a deoptimization down to the machine instructions that caused it.
Idea to Machine43 min9 levels
- 02
Go concurrency, from go keyword to OS thread
What makes goroutines and channels different, the patterns they unlock and the bugs they invite, then down through the G-M-P scheduler, the inside of a channel, OS threads and the netpoller, to the two instructions that make stacks growable.
Idea to Machine45 min8 levels
- 03
Go’s garbage collector, from GOGC to the cache line
Follow a 64-byte cache entry through allocation, concurrent marking and sweeping. Break a collector, tune a heap goal, read real runtime output, and see why Green Tea changes the order in which memory is touched.
Idea to Silicon45 min8 levels
- 04
Rust ownership: the checks and the machine
Follow a batch of log lines through moves, borrow checking, threads and async suspension. See what the compiler proves, what a future stores, and the instructions that remain.
Idea to Machine42 min8 levels
- 05
Zig comptime: the compiler runs your code
Build a tiny binary protocol with types as values, a derived packet codec and a CRC table. Follow ordinary Zig code through compile-time evaluation into the bytes and instructions that survive.
Idea to Machine40 min8 levels
- 06
WebAssembly, top to bottom
Start with real C zlib compressing your text in this tab. Then go down through the JavaScript boundary, the module format and the stack machine to the guard pages and x86-64 an engine uses to run it fast and safely.
Idea to Machine40 min10 levels
Notes
Practical answers in languages and runtimes.
Find why Node and V8 deoptimize a function
Use V8 optimization traces to identify the invalidated assumption, then reproduce it with a controlled input change before changing application code.
Cross-compile C and Zig with Zig 0.17.1
Select the target explicitly with zig cc -target or a build script using standardTargetOptions. Verify the file format separately from whether the artifact runs on the target.
Fix “borrowed value does not live long enough” in Rust
Keep the owner alive through the last borrow use, or return owned data. Five examples cover locals, borrowed structs, closures, temporaries and iterators.
Tune Go GC with GOGC and GOMEMLIMIT
Use GOGC to trade heap growth for collection frequency and GOMEMLIMIT to constrain Go-managed memory. Set container headroom explicitly: Go 1.27.3 does not derive this limit from cgroups.
Find and fix a goroutine leak in Go
Compare goroutine stacks after work has drained, identify the missing exit path, and cancel and join workers before returning.
Other topics
Web and networking
Everything between a URL and a pixel: the protocols that carry bytes across the internet and keep them private and fresh, and the browser machinery that turns them into a page.
12 dives · 10 notes · 8.8 h of reading
AI models
How neural networks learn from data and get shaped into assistants, and the architectures that turn text, images and sound into predictions.
6 dives · 1 note · 4.1 h of reading
AI serving
What it takes to run a model once it is trained: generating tokens fast, fitting weights into memory, coping with long prompts, and connecting models to data and tools.
6 dives · 8 notes · 4.8 h of reading
Systems and hardware
The machine under all the software: how a processor executes instructions, what memory really is, and how a GPU keeps thousands of threads busy.
6 dives · 4 notes · 4.6 h of reading
Infrastructure and operations
Deploying and operating software: Kubernetes workloads, Helm releases, Ansible automation, Raspberry Pi clusters and the practical checks that keep systems running.
6 notes · 0.3 h of reading
Application development
Building applications and data workflows: framework patterns, Django and Wagtail models, Next.js integration, identity schemas and practical data scripts.
5 notes · 0.2 h of reading