In this text, Joe Armstrong answers a message from Luke Gorrie in 2003 where he (Joe) discusses error handling in Erlang, advocating for allowing processes to crash instead of implementing extensive error-checking code. He emphasizes generating clear error messages, sticking to specifications, and using separate processes to observe and correct errors for fault tolerance. The Erlang design mirrors an idealized human organization’s structure, where different roles manage tasks, check quality, and handle errors.

https://dev.to/adolfont/the-let-it-crash-error-handling-strategy-of-erlang-by-joe-armstrong-25hf