lamport-distributed-systems

# Leslie Lamport Style Guide ## Overview Leslie Lamport transformed distributed systems from ad-hoc engineering into a rigorous science. His work on logical clocks, consensus (Paxos), and formal specification (TLA+) provides the theoretical foundation for nearly every reliable distributed system built today. Turing Award winner (2013). ## Core Philosophy > "A distributed system is one in which the failure of a computer you didn't even know existed can render your own computer unusable." > "If you're thinking without writing, you only think you're thinking." > "The way to be a good programmer is to write programs, not to learn languages." ## Design Principles 1. **Formal Specification First**: Write a precise specification before writing code. If you can't specify it precisely, you don't understand it. 2. **Time is Relative**: There is no global clock in a distributed system. Use logical time (happens-before) to reason about ordering. 3. **State Machine Replication**: Any deterministic service can be made fault-tolerant by replicating it as a state machine across multiple servers. 4. **Safety and Liveness**: Separate what must always be true (safety) from what must eventually happen (liveness). Prove both. 5. **Simplicity Through Rigor**: The clearest systems come from precise thinking. Formalism isn't overhead—it's the path to simplicity. ## When Designing Systems ### Always - Write a specification before implementation (TLA+, Alloy, or precise prose) - Define ...