A lot of the major anger is coming from businesses and government and to be completely honest…
If the system your business or government agency has implemented requires 100% up time and relies on a cellular network or any network or power grid for that matter, guess who’s responsible for ensuring that there is adequate redundancy to insure a outage does not occur or is very unlikely to occur…?
Ding ding ding that’s you, you are the one responsible, or the person who you had design it and set the standard and enforce it…
Business and government agencies/services implemented systems with a single point a failure to cut costs, when I absofuckinglutly guarantee that a network engineer brought up that maybe they should add redundancy and was shot down by bean counters.
And now that it’s blown up in their fucking face they have turned around and are trying to redirect attention from shareholders and the public back on to Optus.
Optus fucked up, but no more than if a power line came down when the power company had one of their trucks back into it and the power went out.
If people are going to die if the shit you are designing doesn’t work, or you business is going to loose tons of money, that’s your responsibility to design and implement something that does not have a single point of failure.
Whilst those agencies and businesses do have fault because their DR plans were not adequate, they also likely had paid SLAs with Optus which Optus broke.
The state of IT in Australia is a bit of a joke to be honest and it largely comes down to businesses treating it like an expense that needs to be minimised rather than the cost of actually doing and maintaining business.
A lot of the major anger is coming from businesses and government and to be completely honest…
If the system your business or government agency has implemented requires 100% up time and relies on a cellular network or any network or power grid for that matter, guess who’s responsible for ensuring that there is adequate redundancy to insure a outage does not occur or is very unlikely to occur…?
Ding ding ding that’s you, you are the one responsible, or the person who you had design it and set the standard and enforce it…
Business and government agencies/services implemented systems with a single point a failure to cut costs, when I absofuckinglutly guarantee that a network engineer brought up that maybe they should add redundancy and was shot down by bean counters.
And now that it’s blown up in their fucking face they have turned around and are trying to redirect attention from shareholders and the public back on to Optus.
Optus fucked up, but no more than if a power line came down when the power company had one of their trucks back into it and the power went out.
If people are going to die if the shit you are designing doesn’t work, or you business is going to loose tons of money, that’s your responsibility to design and implement something that does not have a single point of failure.
Whilst those agencies and businesses do have fault because their DR plans were not adequate, they also likely had paid SLAs with Optus which Optus broke.
The state of IT in Australia is a bit of a joke to be honest and it largely comes down to businesses treating it like an expense that needs to be minimised rather than the cost of actually doing and maintaining business.