Erlang's let-it-crash philosophy - applicable elsewhere?

Question

Erlang\'s (or Joe Armstrong\'s?) advice NOT to use defensive programming and to let processes crash (rather than pollute your code with needless gu

Answer 1

IMHO Some developers handle/wrap checked exceptions with code which add little value. It is often simpler to allow a method to throw the original exception unless you are going to handle it and add some value.