I think the book Zen and the Art of Motorcycle put it well. Formal methods are unstoppable but they're also really slow.
A lot of it is incorrect too. For example, there are methodologies to doing software estimation. Some of the more complex ones are less accurate than some of the simpler ones. Nobody really cares that there's a 90% chance that this feature will be completed between 4 hours and 4 months, and a 30% chance that it will be completed in 2 weeks. If asked for an estimation, someone will just toss out the "2 weeks number" because it has the highest odds. Nor do you really want to spend several hours or days narrowing that range, because not only would you still be incorrect, you'll have spent time on estimation that you otherwise would have spent doing work.
Comments
I think the book Zen and the Art of Motorcycle put it well. Formal methods are unstoppable but they're also really slow.
A lot of it is incorrect too. For example, there are methodologies to doing software estimation. Some of the more complex ones are less accurate than some of the simpler ones. Nobody really cares that there's a 90% chance that this feature will be completed between 4 hours and 4 months, and a 30% chance that it will be completed in 2 weeks. If asked for an estimation, someone will just toss out the "2 weeks number" because it has the highest odds. Nor do you really want to spend several hours or days narrowing that range, because not only would you still be incorrect, you'll have spent time on estimation that you otherwise would have spent doing work.