3 ms·
Thanks for the paper. Didn't have it. Just skimming it for now. "legal contracts, and other humanly interpretable specifications, are always stated within a ba
by nickpsecurity 10y ago
Thanks for the paper. Didn't have it. Just skimming it for now.
"legal contracts, and other humanly interpretable specifications, are always stated within a background of common sense, to cover the myriad unstated and unstatable assumptions assumed to hold in force. (Current computer programs, alas, have no common sense, as the cartoonists know so well." (Smith)
Most appropriate quote of the paper for purposes of this discussion. Human negotiators have common sense plus legal precedents (and lawyers) that guide the process to create sensible terms. They might argue over them later but the process works well enough. You'll rarely see something enormously simple and stupid happen. Whereas, computer programs, when asked, will happily divide by zero, overwrite their own system files, or make some prick investing in blockchains richer than deserved. They're idiotic. The part of INFOSEC dedicated to reducing impact of inherently risky and idiotic computers running arbitrary programs has been a miserable failure. The ones using constrained, predictable programs on less risky or idiotic HW/SW combos have a steady stream of good results. Especially in safety-critical industry. One trick is they, like legal contracts, are extra clear on the Why, What, and Where of their operation. The typically implicit assumptions are explicit enough to check with regular brains and smart tooling. Smart contracts will need this property as well.
"consider the following super simple function:"
That function isn't simple because it has floats. I've forgotten too much C to be sure of what the error is. I'm suspecting one or both of two: no sanity check on lower bounds of input value in Celcius, which might affect correctness; errata related to floating point math (esp rounding) which is not decimal math that we teach students to use for conversion functions & likely was in the mental spec developer had in their head. I avoided floating point wherever possible due to its weird issues. Was I close or what was the actual error?
- wolfgke 10y ago> You'll rarely see something enormously simple and stupid happen. Because our society trains all people in this area very deeply. If the society would mainly train people really deeply into mathematics and computer science instead, I believe the situation would be exactly opposite.
- pc2g4d 10y agoLack of bounds check on the input was my first thought, too. Need to deal with NaN sanely, too, but usually that takes care of itself as it propagates through any operations.