Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Maybe we shouldnt run safety critical code of which we dont know what it does. Hard realtimesystems exist for a reason. Sure it would also be nice if we could drive nuclear power plants at home via a smartphone app, so the most qualified expert could help in an emergency, but its simply not a sane idea.

This cop out of "Software gonna have bugs" as a way to evade all liability doesnt hold in any other profession. I dont see why we get special treatment here.



It does hold, in some form or other, in other professions. The EPA formally defines how much cash they're willing to burn to save a human life, which seen from one perspective is an "environment gonna kill people" cop out. Nuclear missile silos have two operators because "people gonna launch nukes". Cars have airbags because "vehicles gonna crash". Every field has risks and risk management, every field has certain steps that they could take for the purpose of safety that are judged too expensive to justify the risk, and part of managing risks in software is that you should plan for bugs and plan to mitigate their impact.

Nobody calls the emergency services out because they assume cars are going to crash and plan accordingly, so why does the software engineering industry get called out for assuming software will go wrong and planning accordingly?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: