I understood the article just fine. The "Let It Crash" philosophy is scale invariant. Please read the last three paragraphs in [0]: "a well-designed applicatio

I understood the article just fine. The "Let It Crash" philosophy is scale invariant. Please read the last three paragraphs in [0]: "a well-designed application is a hierarchy of supervisor and worker processes" and "It handles what makes sense, and allows itself to terminate with an error ("crash") in other cases." I've personally designed and co-implemented mission critical real-time logistics systems which dealt with tens of thousands of events per second, with hundreds of different microservices deployed on a cluster of 14 heavy nodes. Highly complex logic. At first we were baby-sitting the system, until it became resilient by itself. Stuff crashed all the time. Functional logic was still intact. Then we had true silence for months on our pager alerts. I call it anti-fragile and Taleb is right. You can't make a system resilient if you don't allow it to fail. [0] https://wiki.c2.com/?LetItCrash https://wiki.c2.com/?LetItCrash