Technology

Or you could be fired because technically you're the one that caused the outage.

It not going to bring the service online, but it will prevent a full disk from letting you do other things. In some cases SSH won’t work with a full disk.

Sends a message and gets the services ready for potential shutdown. Or implements a rate limit to keep the service available but degraded.

The IT people that want to implement that disaster recovery plan do not make the purchasing decisions. It takes an event like this to get the retards in the C-suite listen to IT staff.

Toyota was the carmaker best positioned for the COVID chip shortage because they recognized it as a bottleneck. They were pumping out cars a few months longer than the others (even if they eventually hit the same wall everyone else did).

It wasn’t just Fukushima. There was a massive flood in Thailand at the same time that shut down a load of suppliers. It was a really bad bit of luck but they did learn from that.

The problem is that leadership doesn’t interpret it that way and just sees “minimizing inventory increases profit!”

Yep. Managers prioritize short-term gains (often personal gains, too) over the overall health of a business.

There's also industries where the "lean" strategy is inappropriate because the given industry is one that booms in times of crisis when logistics to get "just in time" supplies go kaput due to the same catastrophe that's causing the industry to boom. Hospitals and clinics can end up in trouble like this.

But there's other industries too--I haven't looked for it, but I'm sure there's a plethora of analysis already on what Covid did to companies and their supply chains.

In my own impression from the side of software engineering (i.e. the whole discipline rather than just "coding") this kind of thing is pretty common:

• Start with ad-hoc software development with lots of confusion, redundancy, inneficient "we'll figure it out as when we get there" and so on.
• To improve on this somebody really thinks things through and eventually a software development process emerges, something like Agile.
• There are lots of good reasons for every part of this processes but naturally sometimes the conditions are not met and certain parts are not suitable for use: the whole process is not and can never be a one size fits all silver bullet because it's way to complex and vast a discipline for that (if it wasn't you wouldn't need a process to do it with even the minimum of efficency).
• However most people using it aren't the "grand thinkers" of software engineering - software architect level types with tons of experience and who thus have seen quite a lot and know why certain elements of a process are as they are, and hence when to use them and when not to use them - and instead they're run-of-the-mill, far more junior software designers and developers, as well as people from the management side of things trying to organise a tech-heavy process.

So you end up with what is an excellent process when used by people who know that each part tries to achieve, what's the point of that and when is it actually applicable, being used by people who have no such experience and understanding of software development processes and just use it as one big recipe, blindly following it with no real understanding and hence often using it incorrectly.

For example, you see tons of situations where the short development cycles of Agile (aka sprints) and use cases are used without the crucial element which is actually envolving the end-users or stakeholders in the definition of the use cases, evaluation of results and even prioritization of what to do in the next sprint, so one of the crucial objectives of use cases - the discovery of the requirement details by interactive cycles with end-users where they quickly see some results and you use their feedback to fine-tune what gets done to match what they actually need (rather than the vague very high level idea they themselves have at the start of the project) is not at all achieve and instead they're little more than small project milestones that in the old days would just be entries in Microsoft Manager or some tool like that.

This is IMHO the "problem" with any advanced systematic process in a complex domain: it's excellent in the hands of those who have enough experience and understanding of concerns at all levels to use it but they're generally either used by people without that experience (often because managers don't even recognize the value of that experience until things unexpectedly blow up) or by actual managers whose experience might be vast but is actuallly in a parallel track that's not really about dealing with the kinds of technical concerns that the process is designed to account for.

I wonder what happens if the summary is longer than the original text. Negative percentages? Stack underflow?