> Incorrect, optimized (but non-critical) code that fails .1% of the time Only if it fails in known, predictable ways. In that case, I think it falls under the

> Incorrect, optimized (but non-critical) code that fails .1% of the time Only if it fails in known, predictable ways. In that case, I think it falls under the accuracy tradeoff where you define a narrow band of acceptable correctness (99.9% accurate), and correctness is "merely" orders of magnitude more important than performance. If your code fails in unpredictable ways 0.1% of the time, you basically cannot use it. It doesn't matter if it's non-critical: an idle clicker game that has a 0.1% chance of bricking the user's computer or deleting some random data from their system is not usable.