Let it crash philosophy is something a little hard to grasp as a newcomer since usually we are taught to write code defensively. But even crossing that line and getting the idea of how ẁe should work with the guarantees that runtime give us, it has been a terrible experience to work with external tools that don’t/can’t incorporate those concepts.I’ve already worked with Honeybadger and currently been working with Bugsnag and both had the same problem, that are some sort of errors that i don’t care they happened, it’s something my supervision tree will probably take care of. I’ve abstracted this difference as errors and bugs, bugs being the kind of error that i really care about(my code raised on a request and 500ed it) and erros the ones that i not(a worker for a background job library died due to an expected external resource error). I’ve discussed this a little with some of my co-workers but i’d like to know how other people in other contexts deal with it.
So, how do you deal with error reporting services and how you deal with handling expected and unexpected errors?