I've taken a look into the paper (the chapter) and that's not great of a paper unfortunately: https://dev.to/gabrielfallen/a-cold-shower-for-a-cold-shower-237d
In my view, it didn't provide an "extensive literature review" even at the time, and still less than that now, 20 years later. And I don't see how it supports the claim that "formal methods are hard to learn, extremely expensive to apply, and often miss critical bugs".
Besides, I don't see anybody actually claiming "Formal Verification is a great way to write software. We should prove all of our code correct.", and it looks like nobody ever did. Thus it doesn't look like we need a cold shower on this one at all...
I've taken a look into the paper (the chapter) and that's not great of a paper unfortunately: https://dev.to/gabrielfallen/a-cold-shower-for-a-cold-shower-237d
In my view, it didn't provide an "extensive literature review" even at the time, and still less than that now, 20 years later. And I don't see how it supports the claim that "formal methods are hard to learn, extremely expensive to apply, and often miss critical bugs".
Besides, I don't see anybody actually claiming "Formal Verification is a great way to write software. We should prove all of our code correct.", and it looks like nobody ever did. Thus it doesn't look like we need a cold shower on this one at all...