I agree with you in the sense that, after the spectacularly good project, it would have been great to run code gen and get a skeleton to fill in.
I disagree with you in the sense that TLA+ as a language forces you to think about the problem you’re modelling from a very different perspective than how you’d actually write it in an OO/FP/whatever language, and in my experience so far, that has been a very powerful thinking tool. TLA+ doesn’t constrain you to thinking about “how would I write this in Java”, but more in a “how should the communication patterns in this system work” way.
That's probably the most useful result TLA+ can give in comparison to not using it.
Understanding that requirements are impossible after 1-2 weeks of modelling is way better that after 6+ months of coding.
I guess that’s the point where I see so much overlap with tests. It seems like we’re talking about test inputs and test outputs.
Even with IPC or Distributed systems I often break problems down in a way that makes them testable in a local system with repeatable results. It’s not 100% perfect b/c you can’t account for all failure scenarios.
I do see your point though about constraints of the target language.
One of the tricky parts I found was figuring out what granularity to use when writing specifications.
Tests only cover the cases you think of. Proof systems let you validate claims about all possible executions.
I can see the advantage, but I wonder if there’s potential for writing the proofs in the target language, verifying the logic, then building the code, and verifying the code meets the proofs.
Is this something anyone is looking into? I could imagine a macro in Rust for example that is TLA+, that takes standard test input, verifies the logic, then you feed in the real implementations.