How to ask a good question, and How to give good answers.
1. Think carefully before you ask a technical question; Are you asking the _right_ question?
It can often be the case that one asks the wrong question: if so
How to ask a good question, and How to give good answers.
1. Think carefully before you ask a technical question; Are you asking the _right_ question?
It can often be the case that one asks the wrong question: if so you will be bombarded with further questions from members about what you are doing, why you are doing it - everything except an answer to what you needed or wanted to know. When answers drift from the subject [as you see it] then that often indicates that you asked the wrong question.
Learn from this experience; focus. If necessary ask a new and better question.
2. Be clear: put the main question or issue in the subject line and give as much supporting detail as possible in the rest of your message.
It's often helpful to have to think and summarize the issue in the short space available in the subject line. Starting the subject with "Hello all" or "I need help" or anything that does not DIRECTLY address your question is wasting valuable space and not necessary.
3. Give members information; give even more information.
If your question is about failures or problems on machines you are supporting then include any information about research you have already done, or errors you've noted or logged. The work you've already done and the logic behind that work are important here.
Tell members which OS is [or OSs are ] involved and give any other supporting information which may be relevant.
Starting a new discussion with something like "Help, my computer won't boot" and no other information will get you zero replies.
Starting a new discussion "Windows XP failing to boot: suspected disk failure, no disk lights, disk not found" is a major step forward.
Adding information about the tests or diagnostics you've already done gives members something to get their teeth into.
4. Remember the courtesies: be polite, and take the trouble to check back regularly to see if anyone has answered you.
If they have spent time writing an answer and their answer helps you then TELL THEM SO and thank them for their time.
That way others can learn from what has happened. If it doesn't help, or you've already tried their suggestion, say so politely.
If you solved the problem on your own, tell members how you did it.
When the problem is "Resolved" then say so.
Mark the reply that helped fix your issue with “Best Answer”.
If you find the reply in a thread to be usefull. Don’t forget to Spice it up.
There is another great thread on this topic by Scott Alan Miller:
1. Before you answer someone else's question make sure you have read it at least twice to ensure you /really/ understand the question: this is particularly important if you and/or the other person are not using English as a first language.
If others have already posted answers then make sure that you have read and understood what they are saying - that way you will not simply be repeating what others have already said.
2. If you do not understand something in a message - ASK about it!
Don't simply assume that there is something wrong in that message.
3. DO NOT "kidnap" discussions by asking for help on a different topic, do not try to take over other people's discussions.
4. DO NOT use other discussions to promote yourself or your services.
ON LANGUAGE & CULTURE
Please DO remember that this is a global group.
While we all mostly use English as the common language here, not everyone is a native English speaker.
Differences in the way English is used around the world can be very significant and can lead to major misunderstandings; this can even be true within single countries or continents: west coast US English is not entirely the same as east coast English. Canadian usage is rather different to usage in Texas or Florida. US English is different to English in Australia and New Zealand, or Hong Kong or Singapore.
When you read a message that seems strange, outrageous, offensive or just plain wrong please take the time to think about whether or not your perception arises from differences in language and culture: it's just possible that it does. Basically, give other people a little slack!