Algorithm patterns & code templates
End-to-end architecture problems
Design patterns & practical code
Deep dives into core tech
Production systems & operations
TCP, HTTP, TLS, DNS & more
Consensus, replication & more
Kernel, networking & system calls
Quick reference cards for interviews
“Quantify tech debt in business terms: hours lost per sprint, how often incidents happen, or how much deployment lead time has degraded”
“This is the 'messy middle,' too big for startup informality but too small for enterprise bureaucracy. You have to find a careful balance between structure and speed”
The distributed commit log that became the backbone of event streaming
Run code without managing servers. The cloud provider handles provisioning, scaling, and patching.
Lamport clocks tell you 'event A happened before event B' but cannot tell you whether two events are truly concurrent. Vector clocks can. If neither vector dominates the other (one is not component-wise less than or equal), the events are concurrent, and you know there might be a conflict