Earlier quoted context omitted.
> But the main difference would be that failure modes in CS tend to be binary - a piece of code produces the expected result or it doesn't. I think if you’re talking about CS and code you’re right - it’s a very pure and deterministic system. But if you consider software engineering at scale, you do get scenarios where failure states emerge in a gradual fashion, like the OP example of a worn mechanism. An example woul…
I guess my response to that would be that any change of platform - like scaling up, replication, etc - is an alteration of the environment, similar to changing the geometry of your car's wheels by changing their size, getting different shocks or raising/lowering it. Then you could expect failure states to emerge, but that's when you're looking for unpredictable behavior. I think I was just trying to make the point th…
In a previous job in early 2000s they did have some legacy software that was originally written for VAX/VMS and run on an emulator. Even that environment wasn't stable enough so they maintained some real VAX hardware just in case. And as far as I know, the hardware was physically breaking down.