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
“The Incident Commander role exists to coordinate communication, not to be the person who fixes the problem”
“The sweet spot for most engineering managers is 5-8 direct reports. Below 5, the manager lacks enough context to justify the role. Above 8, 1:1s and career development conversations get squeezed and people start feeling invisible”
Google's RPC framework that actually delivers on the 'high performance' promise, built on HTTP/2 and Protocol Buffers
Decouples producers from consumers, allowing asynchronous processing and better fault tolerance
A saga is a sequence of local transactions where each step has a compensating action. If step 3 fails, steps 2 and 1 are rolled back by running their compensating actions in reverse order. This gives you eventual consistency across services without locking resources