Read the fucking logs? Yes, it happened so many times, on so many guys. Something that I always try to avoid.
Say, you hit into a problem, you looked into the log file, you could see a bunch of error messages and stacktrace, you read the first line, you didn't bother to read the second and further.
You tried to change the configurations or something that you thought would make sense but the same (or new) error came out. You spent quite some time on it like an hour or a day.
You asked me / your supervisor to look into it and they found clear error messages or indications somewhere down the error log. You felt sorry, you found yourself stupid to waste so much time, you wished to be in the hall of shame for that day.
If this is a recurring habit of your, can you make "reading logs carefully" as a troubleshooting principle?
No comments:
Post a Comment