What did it ACTUALLY say?
Dec. 30th, 2007 01:58 pmMy latest pet peeve - people that can't answer the following three questions coherently:
3) Why do you think it's not working? ("Wrong results" ONLY works if you have a CLUE what the RIGHT results are!)
2) What were you doing? (No, "Nothing" isn't valid.)
1) What was the ACTUAL error (not "I think it said...")
3) Why do you think it's not working? ("Wrong results" ONLY works if you have a CLUE what the RIGHT results are!)
2) What were you doing? (No, "Nothing" isn't valid.)
1) What was the ACTUAL error (not "I think it said...")
no subject
Date: 2007-12-30 08:22 pm (UTC)no subject
Date: 2007-12-30 08:38 pm (UTC)"Not working" means it's exhibiting only one of an almost infinite number of undesired behaviors, and doesn't specify which. It's a useful answer only it the person trying to help has an intimate knowledge of what behavior was expected. (Zen and the Art of Motorcycle Maintenance still has about the best philosophical explanation of the whole "working"/"not working" concept, and it clearly describes how individual the concept is ..)
I find myself asking "What exactly is it doing at the moment?" a lot .. usually, if I get an honest and detailed enough answer to that, I can track down enough history of the behavior to figure out what's causing it .. but "honest" and "detailed" are both important parts of that story ..
no subject
Date: 2007-12-30 09:31 pm (UTC)Her: It said it didn't go through!
Me: ... The error message said, "It didn't go through"?
Her: Yes.
Me:
You need to call Microsoft right away, and tell them Windows has begun making up its own error messagesI'd like you to try that again for me, please.no subject
Date: 2007-12-31 07:24 am (UTC)no subject
Date: 2007-12-31 05:23 pm (UTC)The real kicker: This came from one of the other sysadmins in my department...
no subject
Date: 2007-12-31 05:47 pm (UTC)no subject
Date: 2007-12-31 05:48 pm (UTC)no subject
Date: 2008-01-01 09:17 am (UTC)