WHEN "LETTING IT CRASH" IS NOT ENOUGH

Summary from the TLDR Web Dev newsletter

Once your app gets into an undesirable state, the best thing you can do is reset it and start from a fresh, well-known, and correct state. Erlang’s "let it crash" philosophy suggests resetting parts of an application upon failure. While effective, it requires developers to manually track and restore application states. Another approach, "durable execution," allows computation to run uninterrupted by storing minimal data for state reconstruction, making local variables resilient even through restarts.