// a technical education platform
THE RUNTIME
THEORY.
Understand what happens behind the code.
A technical education platform exploring the systems, algorithms, architecture, and runtime behavior that make software actually work.
algorithms / runtime / systems / infrastructure
01 — Featured
A deep dive into one system
One request, traced end to end — the kind of article this platform exists to publish.
02 — Latest
New dispatches from the runtime
Recent articles on how systems behave under the hood.
03 — Map
Ten areas, one way of looking
Every topic begins with the same question: what actually happens, and why does it happen this way?
Algorithms
How complexity, data structures, and time really scale.
Runtime & Execution
What the machine actually does with your code.
Backend Engineering
Servers, protocols, and the request lifecycle.
Databases
Storage engines, indexes, and transactions from the inside.
Networking
The distance between two machines, in packets.
Operating Systems
The kernel's view of your program.
Distributed Systems
What changes when one node is never enough.
System Design
Making tradeoffs visible before they become outages.
Cloud & Infrastructure
Servers, containers, and the abstractions on top.
Software Architecture
The decisions that ripple through every file.
04 — Interactive
Watch a request run the stack
Trace an API call through DNS, TCP, TLS, HTTP, a load balancer, a server, and a database. This is the platform's core idea made visible — systems as moving parts, not static boxes. Read the deep dive
trace / request.md
readyThe browser parses the URL and builds an HTTP request. Before a single byte can leave, it must resolve the hostname to an IP address.
05 — Video
The same questions, on screen
Long-form explanations of runtime behavior, systems, and architecture.
HTTP/3 and QUIC Explained
The transport protocol that replaces TCP — multiplexing without head-of-line blocking, connection migration, and 0-RTT.
WatchHash Tables Under the Hood
Load factors, collision strategies, and cache behavior — why O(1) has a constant that can be 1ns or 200ns.
WatchVirtual Memory in One Diagram
Page tables, TLB, demand paging, and copy-on-write — how your 16GB laptop 'has' 128GB of addressable memory.
Watch