4 ms·
Yes. And when a customer complains about an issue, tell them that your software has no bugs and they should reevaluate what they are doing, because obviously, n
by bornfreddy 2y ago
Yes. And when a customer complains about an issue, tell them that your software has no bugs and they should reevaluate what they are doing, because obviously, nothing unexpected happens in your software and any trail of execution that would help developers figure out what happened is just for lamers (see also Go's stance against stack traces).
/s, if it wasn't obvious enough.
I hate software that fails silently because "you don't need logs". It usually shows that it was developed by someone who never had to act as a sysadmin and just never learned the value of good logs. Thinking anyone can predict all the possible ways a service can fail is misguided at best.
- linkdd 2y agoEven bad logs are better than no logs. Because at least, you can grep the source code for the log message and you have a starting point for debugging.
- karmajunkie 2y agoin addition to that, the absence of logs is useful information as well —customer swears they submitted the form? ok show me the request line…
- deleted 2y ago[deleted]
- GauntletWizard 2y agoI did not say "Don't log anything". I said "Stop using logging", and I'll qualify that (though my original post already did) with "So much". You're using logging for a to of irrelevant actions, and you're trying to sort needles from haystacks when you're better off not piling on the hay.