It's an interesting approach to a problem that most of us don't have, and so is not applicable to the majority of people writing software. The key is to unders

It's an interesting approach to a problem that most of us don't have, and so is not applicable to the majority of people writing software. The key is to understand the risk/reward trade-off in their software stack. For the vast majority of software that is written, no one dies if it goes wrong. In fact, for the vast majority of software, it's a minor inconvenience when a bug bites. Because of this, time to market trumps correctness. It's a totally valid trade-off, but just not very satisfying from an engineering perspective.