A lot of times people compare software development in general to the amount of effort that goes into software for safety critical systems in things like airplan

A lot of times people compare software development in general to the amount of effort that goes into software for safety critical systems in things like airplanes or manned spaceflight. What's less talked about is that in those same areas, overall system design also focuses on reducing critical failure points through redundancy, backups, cross-checking between different sources, manual alternatives, fail-safes, etc. I totally agree that putting more thought and care into software development could certainly be beneficial, especially where security is critical. But I think the point of the article is that an alternative, and maybe more realistic, approach is to make critical systems and networks less brittle so an intentional or unintentional software issue isn't the end of the world. Even in airplanes, computers don't always work right. But it (mostly) doesn't result in planes falling out of the sky because the safety of the system as a whole isn't reliant on one piece of software working perfectly 100% of the time.