The map of the Codex
Sixteen study paths, 305 deep dives, drawn as one diagram. Each section is a node — colored by its accent — sized by depth. The arcs are cross-references: where the databases curriculum points at distributed systems, where Kubernetes points at networking, where system design points at everything. Click a section to open it.
Every section, every count
- 01
Databases
B-trees, LSM, MVCC, replication, sharding — fourteen storage internals.
14 deep dives - 02
Distributed systems
Consensus, consistency models, CRDTs, quorums, time.
20 deep dives - 03
Networking
TCP through BGP, twelve protocol deep dives.
12 deep dives - 04
Security
Threat modeling, authentication, secrets, crypto, CVE classes.
5 deep dives - 05
Operating systems
Processes, memory, I/O, the kernel surface.
10 deep dives - 06
Computer architecture
Pipelines, caches, branch prediction, SIMD.
15 deep dives - 07
Languages
Go, Rust, JavaScript — concepts and runtime internals, three languages deep.
87 deep dives - 08
API design
REST, gRPC, GraphQL, the protocols underneath.
11 deep dives - 09
Cloud
AWS, GCP, Azure service internals, plus cross-cloud patterns.
42 deep dives - 10
Kubernetes
Control plane, kubelet, etcd, informers, client-go.
14 deep dives - 11
Observability
Logs, metrics, traces, OpenTelemetry, SLOs, eBPF.
4 deep dives - 12
Performance
USE, RED, queueing theory, profiling, load tests.
8 deep dives - 13
Problem solving
BFS to advanced DP — twenty-five patterns plus the method.
26 deep dives - 14
OOD
Low-level design — seven classic problems modelled.
7 deep dives - 15
System design
Principles, napkin math, nineteen canonical designs.
25 deep dives - 16
AI systems
How LLMs work, inference serving, embeddings, RAG, agents.
5 deep dives
How to use the map
The map is a navigation aid, not a curriculum. Pick a section that matches the question you're answering — "I need to understand a database for an interview" → databases. "My service is hot and I don't know why" → performance. "What does a RAG stack actually do" → AI systems. "I'm planning my first architecture review" → system design. The arcs between sections are honest about dependencies — networking sits under operating systems, distributed systems leans on databases, performance pulls from computer architecture.
Each section starts with its own hub page (the node you click into) which has its own map of deep dives. Three levels of detail, from this overview down to a specific sentence in a specific deep dive.