2 ms·
They're only acknowledging this now? This principle has long been known to be a bad idea; I've articulated this myself and have heard it from others. At least
by kazinator 5y ago
They're only acknowledging this now?
This principle has long been known to be a bad idea; I've articulated this myself and have heard it from others.
At least most lower-level infrastructure pieces should accept only their documented inputs, and loudly diagnose and reject anything else.
As a software engineer, you cover this with test cases: not just happy input test cases but test cases which verify that bad inputs are handled appropriately.
In my job, I write tests which validate that expected assertions go off in C API's. The assert framework can be reprogrammed to execute a longjmp, or a successful process termination: two different ways available to the test case writer to have the code continue after a failed assertion and report a successful test case (assertion was expected).
For anything that is multiply implemented and has many dependencies, the robustness principle is deadly in the long run.