Comment by gobdovan

15 days ago

>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 concrete, or start writing the code.

- If plain text gets too vague, use math. If you want tools to check it, use TLA+ with TLC or Apalache. Quint and stateright.rs are nearby tools in the same area.

---

Materials:

- TLA+ videocourse by Lamport: https://lamport.azurewebsites.net/video/videos.html

- How to win a Turing Award speech: https://www.youtube.com/watch?v=tw3gsBms-f8

- Thinking above the code: https://www.youtube.com/watch?v=-4Yp3j_jk8Q