lamport

- Leslie Lamport Sometimes the problem is to discover what the problem is.

In fact published before Paxos, and studiously ignored by Lamport + shown to be equivalent.

I can't remember which talk it was, but Lamport said for code generation you should look elsewhere.

I remember this from a Leslie Lamport talk posted also on HN a few months ago.

The syntactic analyzer is nice to have but Lamport really pushes the value of writing down your thoughts in formal logic, as an act.

However, Lamport says (and I've found) 95% of specs will only need boilerplate temporal logic, so don't worry about it.

I taught myself through the book Specifying Systems, although Lamport now recommends the TLA+ Hyperbook.

- Leslie Lamport You're not going to find the best algorithm in terms of computational complexity by coding.

- Leslie Lamport You're not going to come up with a simple design through any kind of coding techniques or any kind of programming language concepts.

That something already so well known wasn't "properly" published for nearly a decade was a bit strange, as Lamport himself explains in the page you cited.

I think this quote sums things up "Writing is nature's way of telling us how lousy our thinking is" Leslie Lamport Lamport is a renowned distributed systems researcher, inventor of Paxos, and creator of LaTeX.

You can also use co-inductive types to embed the temporal logic of actions (TLA) in Coq; TLA is the language Leslie Lamport works with for "Specifying Systems".

Repeat for "Leslie Lamport" and then for "Rich Hickey".

Lamport and Voevodsky are in different fields, and use different tools, but that just means that comparing their journeys is all the more interesting.

Lamport's colleague Butler Lampson evangelized the idea to the distributed computing community [19].

Lamport shows (see Assertion 2's Proof in [1]) that given, 1.