Soft disagree, if you know that no inspection has been done, then you are aware that there may be unknown risks and act accordingly. A safety inspection done poorly creates a false sense of security that can be dangerous.
Soft disagree, if you know that no inspection has been done, then you are aware that there may be unknown risks and act accordingly. A safety inspection done poorly creates a false sense of security that can be dangerous.
Or when the overhead of the debugger causes the issue to never happen
He did say he wanted to sleep with his daughter…
Also, women tend to enjoy their time with a dildo
Your average Microsoft error “error 37253” is worthless to me
This is a security thing. A descriptive error message is useful for troubleshooting, but an error message that is useful enough can also give away information about architecture (especially if the application uses remote resources). Instead, provide an error code and have the user contact support to look up what the error means, and support can walk the user through troubleshooting without revealing architecture info.
Another reason can be i18n/l10n: Instead of keeping translations for thousands of error messages, you just need to translate “An Error Has Occurred: {errnum}”
oh and the ads run into playtime, so once the commercials are done, they give you a 30 second recap of what you missed, then back to commercials because the coach called a time out