I totally disagree.<p>Sure, usually the most graceful thing to do is exit and hope a human fixes it. But that&#x27;s usual because the usual condition is that sudden failure is NBD and a human is right there to screw with it.<p>That&#x27;s becoming less common, though. When software was mostly something running on a PC doing some boring office task, reliability didn&#x27;t matter. But as software is running our airplanes, our cars, our medical devices, and even, as with implanted pacemakers and insulin pumps, our bodies, then reliability gos from NBD to BFD.<p>We see the way forward with things Chaos Monkey [1] and crash-only software [2] and the sort of design for failure you see in things like Agent supervisor hierarchies [3], where the way to reliability is through designing for failure recovery from the beginning and testing thoroughly to make sure it really happens.<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;Netflix&#x2F;SimianArmy&#x2F;wiki&#x2F;Chaos-Monkey" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Netflix&#x2F;SimianArmy&#x2F;wiki&#x2F;Chaos-Monkey</a><p>[2] <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Crash-only_software" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Crash-only_software</a><p>[3] <a href="http:&#x2F;&#x2F;doc.akka.io&#x2F;docs&#x2F;akka&#x2F;snapshot&#x2F;scala&#x2F;fault-tolerance.html" rel="nofollow">http:&#x2F;&#x2F;doc.akka.io&#x2F;docs&#x2F;akka&#x2F;snapshot&#x2F;scala&#x2F;fault-tolerance....</a>