Unless you work in Education
There isn't a soul around this time of year, no one to shower you with gifts and praise, should be moved to September 29th to include all sysadmins...
System Administrator Appreciation Day is here – so what lovely gifts did your employer lavish you with today? Did you arrive at work to a guard of honor? A case of Château Lafite Rothschild? A free holiday? Last week we previewed the special day, which is always celebrated on the last Friday in July, 24 hours in which …
re: "Just for once RTFM"
A-men, brother. Lost count of the number of times I had to bite my tongue to keep from responding "I answered your question, I posted the answer where you could see it, but I can not read it for you and I can not understand it for you." I get that not everyone has the same skills and strengths, and that not everyone has a technical background (or interest), but even so I am given to believe that some people are more interested in kvetching than in having a solution. (Not a sysadmin, btw -- far from it -- but the one on whom interwebby tasks get dumped.)
or to ask even the most basic diagnostic questions such as "What is the error message?"
This is the one I wish I didn't have to ask so often. People often come to me reporting either "It gives me an error", or with some inaccurate paraphrase of the error text. It's on your screen and you're calling me. Is it too much to ask that you call me before you dismiss the message? If you're calling me later, take a screenshot, write it down, copy it into an email, leave the box open, whatever you need to do so I get the text the computer wanted me to see.
Not long ago, a user translated "This site has an invalid security certificate because it has expired" into "My antivirus software wants to control my system's certificates". I'm not even a sysadmin or helpdesk person, but I still get this too often. My profound sympathies to those for whom this is an even more frequent experience.