About
undefinedstack publishes long, visual deep dives into how technology works.
Each dive picks a single topic, such as a protocol, a runtime or a piece of hardware, and follows it from the reason it exists down to the lowest layer that still matters.
The dives are written for engineers who already use these things every day and want to know what happens underneath. Where a diagram explains something better than a paragraph, there is a diagram. Where stepping through it by hand explains it better than a diagram, there is something to run.
How a dive is organised
A dive is a sequence of levels, read in order. Most dives descend through the stack, so their levels are tagged with the layer they sit in:
- Idea
- What you want to happen, and why anyone built this.
- Interface
- The language, API or protocol surface you actually touch.
- Runtime
- Engines, schedulers and state machines that make the interface real.
- System
- Kernels, sockets, threads and the network stack.
- Machine
- Instructions, registers, frames and bytes on the wire.
- Silicon
- Gates, clocks, voltages and electrons.
The stack on the home page draws every dive as a line through these layers, one tick per level, and the depth strip next to each dive shows how far down it goes. Not every subject is a stack, so a dive can also skip the layers and use whatever structure explains it best.
Topics and paths
Dives and practical notes are grouped into topics. Where a topic has dives, its path suggests a reading order in which each dive builds on the ones before it. When you finish a dive, the page suggests the next one on its path and a few related dives from elsewhere.
- AI models 6 dives · 1 notes
- AI serving 6 dives · 8 notes
- Web and networking 12 dives · 10 notes
- Systems and hardware 6 dives · 4 notes
- Languages and runtimes 6 dives · 5 notes
- Infrastructure and operations 0 dives · 6 notes
- Application development 0 dives · 5 notes
Reading progress
Your browser remembers how far you got in each dive, so the home page can offer to pick up where you left off. That record stays in your browser's local storage. Nothing is sent anywhere.
Corrections
These dives simplify on purpose, but they should never be wrong. If you find a mistake, please open an issue on the site's GitHub repository.