3 ms·
There’s a huge misunderstanding that pops up in every discussion about “formal methods.” These methods are not perfect silver bullets to guarantee bug-free sof
by mbrock 8y ago
There’s a huge misunderstanding that pops up in every discussion about “formal methods.”
These methods are not perfect silver bullets to guarantee bug-free software forever. They are supposed to be useful engineering tools that help you think and verify your thinking especially for tricky corner cases and interactions.
So then it’s a bit like “Why would I think about the code I’m going to write when I could later make a mistake in implementing what I though?” Well, even so it has advantages over not thinking.
Not to suggest that “formal methods” are the only way of thinking. They’re just not really what people imagine they are when they criticize them.
- phtrivier 8y agoFair enough. If you have experience, what would be the rebutal to my fear of the "catch-22" ? What I mean is, how often does it happen that you think about a problem right, but fail to transcribe that in a formal method, you gives you either too much confidence in a model that does not work, or makes you feel you have wasted your time on mental self-molesting ? How do you approach "experimenting" with formal methods to avoid this risk ?