tomthecreator

5 ms·

1.
by tomthecreator 1y ago
I’m curious about the practical workflow after you’ve written and verified a TLA+ spec. How do you go from the TLA+ proof to actual code? Is there any established process or best practices for translating the spec into implementation while
2.
by tomthecreator 1y ago
There's a PDF version linked at the top of the article, it's actually much better typeset.
3.
by tomthecreator 2y ago
I wonder the same about HN. Has anyone done this kind of analysis? Me good LLM
4.
by tomthecreator 3y ago
To rebind it to Escape of course. :D Works wonders if you're using vim or vim mode somewhere.
5.
by tomthecreator 5y ago
For anyone not using `merge.conflictStyle = diff3` I highly recommend trying it. It removes a lot of ambiguity when dealing with conflicting changes. And now they introduced `zdiff3` which looks even better, will be trying it once I update.
6.
by tomthecreator 5y ago
Pretty sure the "you're a liar" is just a convenient way to blow it off without going into details. The buy was probably already questionable even for $50m, a number Steve probably already knew even before they entered the ro
7.
by tomthecreator 6y ago
The solution is the same as in many other programming languages: adopt a coding standard and enforce it in an automated fashion, i.e. in the CI/CD pipeline. Code style then becomes mostly a non-issue and not an object of discussion. In
8.
by tomthecreator 6y ago
I'm really sorry olivdums, but it seems I cannot read your blog post because it's behind Mediums paywall. :)
9.
by tomthecreator 7y ago
Probably "invaded".