I am a software program engineer myself, and because of this we’ve Acceptance/Preproduction environments, that we will see and monitor down these sorts of configuration errors or bugs.
When pushing new code, this primary goes to acceptance and right here we check the software program and see if it nonetheless works because it ought to, it will occur in a couple of days, then we put it up for sale to PreProduction and check once more what occurs to the software program right here , with this we take note of our metrics and logging. We’re solely promoted to Prod once we are 100% certain that this works nicely, which normally takes a number of weeks.
So a configuration error like this is able to have surfaced in a short time in our course of earlier than it ever made it to Manufacturing.
Sure, you can not write error-free code, however you’ll be able to detect it early after which not burden your prospects with it.
I’ve actually pushed loads of bugs to Acceptance/PreProd, however that is what these environments are for, so our prospects have the least quantity of downtime/annoyance.
By the way, an replace like this must be delivered as an replace and never as a compelled replace, suppose a config file is pushed which might trigger much more injury, so you’ll be able to destroy all ASUS routers, suppose this server was ever hijacked is completed by a malicious individual, with this you’ll be able to kill all routers from ASUS, that is what I discover most annoying about this drawback.
I feel that with that information you’ll be able to cost fairly a couple of euros per hour as a advisor.
I completely do, don’t fret about that. 
[Reactie gewijzigd door Akamatsu op 20 mei 2023 15:46]
