2 ms·
Those who write 24/7 continuous pipelined processing numerical code for signal process and instrument monitoring are very interested in robust code. This is al
by defrost 4y ago
Those who write 24/7 continuous pipelined processing numerical code for signal process and instrument monitoring are very interested in robust code.
This is almost but not quite secure code - the thread in common is that secure and robust code both have to sensibly handle and happily continue in a known state no matter what the input.
Hackers use fuzzers to concoct evil input that forces exploitable states.
The real world applies sod's law to any input that comes from sats, planes, instruments, etc.
Power flucuations, lightening strikes, disconnected wires left dangling and sparking, N+10 hard resets where N is a number so ridiculous nobody would ever turn it on and then off again quickly that often, ... etc.
When you circle back on any such signal collation for analysis, image generation, cross reference poor handling of unexpected input will cause such a mess that inevitably the habit develops to code excessively defensively, as too much paranoia is rarely enough.