// about
Most programming education asks how to use it.
We ask what actually happens.
The Runtime Theory is a technical education platform about the machinery of software: what a function call costs, why a database is shaped like a tree, how a packet becomes a rendered page. Not recipes — mechanics.
The idea
Every system is a chain of runtime events
An API call is not one thing. It is a DNS lookup, a handshake, a key exchange, a read, a write, a queue, a schedule — each with a cost, each with a failure mode. Education that hides those layers produces engineers who copy patterns; education that exposes them produces engineers who understand tradeoffs.
We explore
- Algorithms
- Runtime behavior
- Systems
- Architecture
- Distributed systems
- Infrastructure
- Performance
How we write
Editorial principles
- 01
Trace the system
Every explanation follows the data — through the stack, the network, the disk. If a claim can't be traced, it isn't an explanation.
- 02
Prefer first principles
What is this thing actually made of? Memory, bytes, time, tradeoffs. Start there and everything else follows.
- 03
Show the tradeoff
Every design decision is a choice between failure modes. We name what you gave up to get what you got.
- 04
Code that runs
When a concept can be demonstrated, we demonstrate it. Reproduce in five minutes beats assert in five paragraphs.
- 05
Depth over breadth
One system understood end to end is worth more than ten landing pages of basics. We publish less, we publish deeper.
Who it's for
For engineers who ask 'why'
If you can already write software and you want to understand the machines running it — the kernel schedules, the packet queue, the buffer pool, the cache line — this platform is written for you. No certification, no clickbait, no '10x' anything.
Understand what happens behind the code.