Leslie Lamport: Thinking Above the Code

Channel:Microsoft Research · Length:59:50 · Published:2014-07-15 · Views:404256

Watch on YouTube

Summary

Leslie Lamport argues that programmers, like architects, should write rigorous specifications before coding, especially for concurrent and distributed systems. The talk introduces the case for writing specs (the TLA+ mindset) as a way of thinking above the code.

Why HN recommends it

HN points people to it as Lamport's own case for thinking and writing a spec before coding, and as an entry point to TLA+.

He's just saying that you should think before you code and that most specifications should be just a few sentences stating what you intend to do. — HN, 2017

Software architecture & design · Distributed systems · Logic & formal methods

Subtitles (excerpt)

ladies and gentlemen please welcome judith bishop good afternoon everybody welcome back to the plenary session of the Microsoft faculty summit it's my great pleasure to introduce to you today Leslie Lamport who's a principal researcher at our Microsoft Research Silicon Valley lab so students and faculty who have taught operating systems courses as well as anybody who's really used a computer will have benefited from Leslie's work on logical clocks safety and liveness sequential consistency and many other parts of operating systems which laid the basis for the safe operation of the computers that we have today as they moved from the single desktop to the large number of interconnected devices we have Leslie before he joined Microsoft was a member of certain various prestigious institutions he was at MIT at Brandis University and at companies such as Dec Compaq and SR I in his career he has also received several honorary doctorates and he has tried very hard to help scientists see their workers beautiful and for that purpose he also developed something that I think you all know very well which is let ik he's now going to go on and try and persuade engineers that there's something else that is beautiful in

On Hacker News

I've invested a fair amount of time into learning TLA+, have bought Hillel Wayne's book (Practical TLA+), and found his stuff super valuable. However, if I could do it again, I would have started in the following order: - 1. Watch [VIDEO] - 2. Watch all of [LINK] - 3. Work through examples on [LINK] I'm normally not a huge fan of YouTube over books / web sites, but in this case the best content c… — b_fiive, 2022-09
>He argues that conceptual integrity comes from both simplicity and straightforwardness If you want to follow this advice, I think Leslie Lamport's formulation is the most concrete. His version is: - Write down a small model of what you are about to build before building it. - Try to see how that model could fail. If it still looks good, either make the spec/design doc/model clearer and more conc… — gobdovan, 2026-05
Most of the real world distributed systems would have some videos in some conferences: Spanner: [LINK] Chubby: [LINK] Anything Leslie Lamport: [VIDEO] [LINK] Also the Distributed system course at MIT is fantastic. The labs are also great way to get your hands dirty with distributed system. The link to the class schedule is here: [LINK] — kediz, 2020-06
No. Have a look at this video. It's worth it. He's just saying that you should think before you code and that most specifications should be just a few sentences stating what you intend to do. Code as a blueprint is not the same. [VIDEO] — discreteevent, 2017-09
Short answer: try starting with TLA+. I'm working on this. My colleague, who is mentoring me, is the one who's finishing his PhD in software engineering. It's his guidance that has helped me so I don't have a good answer for how to teach yourself yet. We're working on a project to create specifications for Openstack and are learning a lot by working together on how formal specifications could be … — agentultra, 2016-03

Related videos