Topics / systems
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.
- How a microprocessor works, 9 levels · 50 min · Idea to Silicon
- Memory, from malloc to a DRAM cell, 9 levels · 50 min · Idea to Silicon
- From gcc main.c to main(), 7 levels · 42 min · Idea to Machine
- Atomics, from a log queue to a store buffer, 8 levels · 42 min · Idea to Silicon
- What a single read() costs, 8 levels · 38 min · Idea to Silicon
- How a GPU runs a kernel, from threadIdx to DRAM, 9 levels · 42 min · Idea to Silicon
The path
Read in this order and each dive leans on the ones before it. Every dive also stands on its own.
- 01
How a microprocessor works
From a line of C to the transistor: the instruction set contract, a RISC-V CPU you can clock by hand, the datapath, pipelines and caches, adders built from logic gates, and the switch at the bottom of it all.
Idea to Silicon50 min9 levels
- 02
Memory, from malloc to a DRAM cell
Follow one malloc(64) all the way down: the allocator's free lists, virtual addresses and page faults, the page-table walk and the TLB, cache lines, DRAM banks, and the leaking capacitor that finally holds your bit.
Idea to Silicon50 min9 levels
- 03
From gcc main.c to main()
A call begins as five bytes with a hole. Follow a tiny C program through ELF objects, symbol resolution, relocation, the PLT and GOT, and the loader that makes those bytes runnable.
Idea to Machine42 min7 levels
- 04
Atomics, from a log queue to a store buffer
Two threads write, then read. Both can read the old value. Follow a log record through a lock-free queue to understand the language contract, compiler instructions, store buffers, and the cache lines moving between cores.
Idea to Silicon42 min8 levels
- 05
What a single read() costs
Follow one HTTP request through a privilege boundary, a sleeping thread, epoll’s ready list and io_uring’s shared rings. Three ways to serve 10,000 connections, down to registers and the packet that wakes a core.
Idea to Silicon38 min8 levels
- 06
How a GPU runs a kernel, from threadIdx to DRAM
Follow a CUDA thread into a warp and onto an SM. Make branches diverge, scatter a memory request across sectors, and fix a transpose one bank conflict at a time.
Idea to Silicon42 min9 levels
Notes
Practical answers in systems and hardware.
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.
Detect false sharing with a runnable C benchmark
Compare adjacent atomic counters with cache-line-separated counters, then use perf c2c to locate contended lines when PMU access is available.
Why ldd is unsafe on untrusted binaries
Inspect ELF dependency metadata with readelf or objdump instead of invoking the loader. Use LD_DEBUG only when you intentionally execute a trusted program.
Find what a process is waiting on with strace
Trace the blocked syscall, follow its file descriptor and identify the thread or peer that must wake it. Use syscall duration rather than summary CPU time to measure waiting.
Other topics
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
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
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
Languages and runtimes
The work a language runtime does on your behalf: scheduling goroutines, collecting garbage, and running portable bytecode safely and fast.
6 dives · 5 notes · 4.5 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