Leslie Lamport podcast appearances

Subscribe on: iTunes | Spotify | Android | YouTube Leslie Lamport is an American computer scientist. Lamport is best known for his seminal work in distributed systems and as the initial developer of the document preparation system LaTeX. Leslie Lamport was the winner of the 2013 Turing Award for imposing clear, well-defined coherence on the seemingly chaotic behavior of distributed computing systems, in which several autonomous computers communicate with each other by passing messages. He devised important algorithms and developed formal modeling and verification protocols that improve the quality of real distributed systems. These contributions have resulted in improved correctness, performance, and reliability of computer systems. https://media.blubrry.com/5minutementor/5minutementor473546891.files.wordpress.com/2019/08/6-leslie-lamport.mp3 Transcript: ES: This is 5 Minute Mentor, a podcast where you’ll get advice from prominent engineers, authors, artists, and more in 5 minutes or less. LL: I’m Leslie Lamport from Microsoft Research. I’ve been a researcher most of my adult life, that means I’ve primarily been a writer and also a performer. I’ve written papers and I’ve performed talks at conferences and other venues. I’ve been successful because I’m a pretty good writer. LL: Good writing will be crucial to your success. The most obvious reason is because people will judge you by your writing, not just by reports or papers that you write, but also by your emails and texts. What does it tell you about a person, if he sends you email with lots of errors, and with sentences that make no sense? LL: Learning to write well takes practice. You have to think before you write, and then you have to read what you wrote and think about it. And you have to keep rewriting, re-reading and thinking, until it’s as good as you can make it, even when writing an email or a text. LL: A less obvious reason to improve your writing, is to improve your thinking. You should think before you write. You should think before you do anything, because it will help you understand what you’re doing, which will help you to do it better. And as someone said, “Writing is nature’s way of showing you how fuzzy your thinking is.” If you think you understand something, and don’t write down your ideas, you only think you’re thinking. To think clearly, you need to be able to write down your ideas clearly, which requires being able to write well. LL: Learning to write well will improve your thinking. And learning to think better, will improve your writing. It’s a virtuous cycle. You have to write better to think better to write better. And you should start that cycle now, by trying to write better. References: <a href="http

TLA+ is a formal specification language. TLA+ is used to design, model, and verify concurrent systems. TLA+ allows a user to describe a system formally with simple, precise mathematics. TLA+ was designed by Leslie Lamport, a computer scientist and Turing Award winner. Leslie joins the show to talk about the purpose of TLA+. Since its creation in 1999, TLA+ has been used to discover bugs in systems such as Amazon S3, DynamoDB, Xbox, and Cosmos DB. “TLA” stands for “temporal logic of actions”, a logical system that can be used to describe the behaviours of concurrent systems. This podcast is meant as a brief introduction of TLA+. To go deeper, check out the TLA+ website and the TLA+ video course (note: these videos are highly entertaining because of Leslie’s dry, unpredictable sense of humor). The post TLA+ with Leslie Lamport appeared first on Software Engineering Daily .

This episode is a republication from my interview with Leslie Lamport on Software Engineering Radio. Leslie Lamport won a Turing Award in 2013 for his work in distributed and concurrent systems. He also designed the document preparation tool LaTex. Leslie is employed by Microsoft Research, and has recently been working with TLA+, a language that is useful for specifying concurrent systems from a high level. The interview begins with a definition: a distributed system is a multiprocessor system in which the time required for interprocess communication is large compared to the time for events within a single processor–in other words, it takes longer for interprocess communication than it does for a process to look at its own memory. Alternatively, a distributed system is one in which processors communicate by sending messages. Leslie goes on to talk about how he became interested in distributed systems, and describes the story behind his paper about the Paxos algorithm. The goal of Paxos is to maintain consensus in an environment with unexpected faults (otherwise known as Byzantine faults). After the discussion of Paxos, Jeff asks Leslie about his recent talk “Thinking for Programmers,” which emphasizes the benefit of having a specification prior to writing actual code. “Specification” can mean a variety of things, but predicates and next-state relationships provide a mathematical rigor that is well-suited to distributed and concurrent systems. The conversation concludes with Jeff asking Leslie about how a programmer can build the mental resolve to work through a difficult problem. The post Distributed Systems with Leslie Lamport appeared first on Software Engineering Daily .