3 ms·
About that, the number of developers that can’t read, or even understand the value of, a stack trace is also astonishing. If only I had a penny every time some
by Too 4y ago
About that, the number of developers that can’t read, or even understand the value of, a stack trace is also astonishing.
If only I had a penny every time someone sent me a “log of the error”, that only contains the final line with the unhelpful message saying nothing but KeyError.
- vladvasiliu 4y agoForget stack traces. I've met multiple "web developers" (actually working on the backend or "full-stack", building API servers and whatnot) who came complaining about this or that server being "unreachable" and could I check it's up / whether the firewall allows them through. Only to find they were getting HTTP 404 errors or the like. Which were explicit in the errors they'd show me.
- lamontcg 4y agoAt prior work we removed stack traces from the default error output because it was thought to "scare" too many users. Then for years almost without fail when an error was pasted into a GH issue it would include the big "If submitting a bug report, please include the full stack trace at /var/log/stacktrace.out" message--without the stacktrace. I added some whitespace around it and all caps to it and still nobody read it.