2 ms·
I think it's about fault-tolerance. So "programming" in the Software 2.0 world is basically training a model. Which isn't a task with an end. You stop when you
by marcus_holmes 4y ago
I think it's about fault-tolerance.
So "programming" in the Software 2.0 world is basically training a model. Which isn't a task with an end. You stop when you're bored, or when it passes a given level of accuracy, not when it's "completely trained" because it will never get to 100% accurate.
In e.g. speech recognition, handwriting recognition, speech synthesis, drawing pictures, writing a response to a human's question, all those messy "organic" problems, this is fine. A 99.9% accuracy rating at e.g. speech recognition is better than humans do.
But there are problems that absolutely need 100% accuracy, and you can only get that if you code it up the old-fashioned way (though probably not Agile - I love my iterative development cycles but they're equally prone to not quite getting it 100% right).
- a-dub 4y agommm... i disagree. fault tolerance is more of a reliability property that sits outside of the performance of a discrete logic or signal processing system, it describes how well a system can remain functioning in the face of adverse conditions like internal failures, hardware substrate failures, dependency failures, adverse inputs, etc. but... yeah, some problems have continuous performance variables (typically ee'ish) and others have discrete ones (typically cs'ish). the discrete account ledger either computes the correct value or it does not, where many signal processing problems have to contend with noise and are allowed to produce a wide range of noisy outputs and therefore their measures of correctness are based on statistical arguments.
- marcus_holmes 4y agothanks for putting my point better than I ever could :)