2 ms·
I would say that most software doesn't have to be correct to be useful. There are exceptions, like anything to do with cryptography. You might say that the sa
by kragen 5y ago
I would say that most software doesn't have to be correct to be useful. There are exceptions, like anything to do with cryptography.
You might say that the same can be true of calculations; after all, calculations about the contingent universe (as opposed to, say, number theory) are always based on data incorporating some uncertainty. But there are two key differences:
① I don't put up a slide showing all the intermediate values of the variables in my program in order to make an argument for something. Instead, I try to show my chain of reasoning in enough detail to be convincing and to expose any relevant potentially incorrect assumptions or reasoning steps I've made so that others can find my errors, without including trivial or irrelevant details. Including trivial and irrelevant details makes it harder, not easier, to find relevant incorrect assumptions or reasoning steps.
That's why I question the motivation of people who include those in their slides: it sounds like they're attempting to make their argument so complex that there are no obvious errors, rather than so simple that there are obviously no errors.
② A 10% uncertainty in an input datum can be traced through the calculation from beginning to end and will often result in a 10% or 21% uncertainty in the result, or even less. (And where that's not the case the sensitivity should be called out.) A calculation that's simply incorrect—for example, treating millions as thousands, or forgetting to divide by the relevant denominator—commonly produces results that are off by multiple orders of magnitude.