4 ms·
I agree, a simple string from the error doesn't help debugging at all. This happens a lot in production environment, in which developers are too lazy to write a
by halfer53 7y ago
I agree, a simple string from the error doesn't help debugging at all. This happens a lot in production environment, in which developers are too lazy to write any useful debugging information, all we got left is a simple "get_foo() returns error" in the log, it doesn't help with the debugging at all !!!
- nomel 7y agoSound familiar. I had a boss that wanted to clean up our error messages and stack traces from our library/api and make them cleaner and more useful. To make it cleaner, he wanted to absorb the whole stack for any error raised in our library and only print the error text. To make them more useful and helpful, he wanted us also include some guides on how to debug and solve the problem, based on the error, in the error text. Fortunately I was able to convince him this would make things difficult for everyone, in a calm collective way.