Leslie Lamport reveals that the concept of using state machines to build distributed systems was a key part of his seminal "Time, Clocks" paper. However, this practical idea was completely overshadowed by the more theoretical "happened-before" relation. He had to reread his own paper to confirm he wasn't "going crazy" when people claimed it wasn't there.

Fei-Fei Li's lab believed they were the first to combine ConvNets and LSTMs for image captioning, only to discover through a journalist that a team at Google had developed the same breakthrough concurrently. This highlights the phenomenon of parallel innovation in scientific research.

Bitcoin wasn't created in a vacuum. Its founder, Satoshi Nakamoto, explicitly identified in early emails that the core technical challenge was solving the "Byzantine agreement" problem, a long-standing issue in distributed computing research. This reveals the deep, often unacknowledged, scientific roots of modern blockchain technology.

Early distributed systems relied on users locking replicas, which was fragile as it depended on remote actors. Barbara Liskov's key insight was to shift control to the replicas themselves, making them responsible for coordination. This paradigm shift was foundational for modern, robust replication protocols.

Liskov and Leslie Lamport independently created the same distributed consensus algorithm. However, Lamport's "Paxos" became far more famous than Liskov's "ViewStamp Replication." She credits this to Lamport's extensive speaking and writing on the topic, illustrating that evangelism can be as crucial as the invention itself for an idea's widespread adoption.

Lamport emphasizes the critical distinction between an algorithm and code. An algorithm is the abstract, high-level solution, while code is just one implementation. He argues that engineers often mistakenly jump directly to code, conflating core synchronization problems with irrelevant implementation details, which leads to flawed systems.

To ensure his critical work on fault tolerance was widely understood, Lamport created the "Byzantine Generals" narrative. He learned from Dijkstra's "Dining Philosophers" that a memorable story is key to an idea's popularity and adoption, even if the underlying problem is complex and highly technical.

Barbara Liskov recalls a time when top database and operating systems researchers attended the same small conferences. This proximity made it easy to see the field as a whole and borrow concepts, like applying database transactions to distributed systems—a process much harder in today's fragmented, hyper-specialized academic landscape.

Leslie Lamport challenges the notion that Raft is superior to Paxos because it's more "understandable." He points out that a bug was found in the very version of Raft that students preferred, suggesting their understanding was superficial. For Lamport, true understanding means being able to write a proof, not just having a "warm, fuzzy feeling."