> your program should just fail instead of giving a ton of messages and recovering I would bet that he was right in that situation, but that he was also making

> your program should just fail instead of giving a ton of messages and recovering I would bet that he was right in that situation, but that he was also making a nuanced statement. Not all code should fail loudly, but when it should, "recovering" can sometimes be a distraction from a very real problem that needs to be addressed by the right person.