I have been organized by 9CBS, the art of questioning, I have been passed on online, I have seen it in I have not graduated, I have made small modifications for 9CBS, mentioned inside.
Http://community.9cbs.net/expert/topicview.asp?id=3229596
What kind of answer can you get when we ask a technical issue? This depends on the difficulty of the answer, which also depends on the method you ask. A good question method can maximize your most wanted answer and solve your problem.
I don't want to cover some people's contempt - they don't want to think, or don't do what they should do before you ask. This kind of person will only murder - they are only willing to request, never pay, unprepared, the answer, the answer, can use the time to use in more interesting questions or more worth answering. We call such a person "loser" (due to historical reasons, sometimes it will spell "lusers").
A. What should I do before answering? (Before you ask)
Ask yourself before the technical problem is proposed:
1. Use the help of the system, try to find an answer to solve the problem; 2. Looking for an answer in FAQ (a well-maintained FAQ can be inconvenient); 3. Search online online, your problem may have touched When you go to Google, find it; 4. Consult your friends who are paid by this.
When you ask questions, you must first explain what you have before this; this will help to establish your image: You are not a beggar who is inused, do not want to waste others. If the questioner and the answer person can learn something from the answer, the solutioner is more happy to answer his questions.
Thoughtful thinking, ready for your problem, the question of the grass rate can only get an answer to the grass rate, or you can't get any answers. The more you show your efforts to solve the problem before seeking help, the you can get a substantive help.
On the other hand, you are willing to do something in the process of finding the answer, it is a very good start. "Who can give some prompts?" Because you seem to have a correct direction, you have the ability and determination to complete it, but it is not a step in one step.
B. How should I ask questions (When You ask)
Care to choose a zone
Carefully choose to ask questions. If you are likely to be described below, you are likely to be ignored or as a loser:
1. Post your problem in the forum or zone that is not between Feng Massow; 2. Discussing the high-level tip of the forum posted a very primary question; vice versa; 3. At too many different seragues;
Use the vocabulary, the syntax is correct, spelling
() We found in experience, careful writers are usually the thinking of horses and tigers (I dare to pack). The problem that answers the heart is not worth it, the solutioner would rather turn the time elsewhere.
() The correct spelling, punctuation and case is important. More general, if your question is written like a half illiteracy, you are likely to be ignored.
() If you ask questions using non-nominal forums, you can make a small mistake in spelling and grammar - but you can't think about the slopes (right, the answer can figure out the differences.)
() Use the meaning of implied, describe the accurate title, in question, the topic title within about 50 words is the golden time to grasp senior experts. Don't use the chatter "helping" (let alone "help !!!!!" "" "" "" "" 地 "is to waste this opportunity. Don't want to use your level of pain to touch the answer, don't use the space instead of the problem, even if it is an extremely short description. Description Unclear question:
Help! My Windows 98 cannot be displayed normally! ! ! ! ! !
Recommended expression:
Help! My Windows 98 has always been very good, but recently entered the system after the screen, the mouse is not listening.
Accurate description, large information
1. Carefully describe the symptoms; 2. Provide a problem that occurs (machine configuration, operating system, network topology, application settings); 3. How do you study and understand this problem before you ask questions; 4. Explain what steps you have taken before you ask questions; 5. Row colleges have recently made hardware, software changes.
Simon Tatham wrote an excellent essay called "How to Effective Report Bug". Strongly recommend you to read it.
Not too much
You need to provide accurate and effective information. This is not asking you to simply put the ton of error code or data completely dump in your question. If you have a large and complicated test condition, try to cut it as much as possible. There is at least three points everywhere.
First, you have made your efforts to simplify the problem, which allows you to answer the opportunity to increase; second, simplify the problem to increase the opportunity to get useful answers; third, in the process of refining your BUG report, Maybe you can find a problem or make corrections.
Description Unclear question:
Hello everyone! There is an XP machine to see you, you can't open it! What should this be the best?
Recommended expression:
In a local area network, the server is Windows 2000 Server. The client is Windows XP Pro, the server ping client, can ping. But search computers can not find the client. Excuse me, what is this question? How to deal with it? Thank you!
Symptom symptoms in time
For the most helpful clues to find out, it is often a series of operations before the problem, so your instructions should include steps, as well as the response of the computer until the problem is generated. If your description is long (more than four paragraphs), the problem will help, followed by the time order. This will let people know what to find in your description.
Understand what you want to ask
There is no margin, and there is almost no time black hole. People who can give you useful answers are also the most busy people (they are busy because they must do most of them.). Such people don't have a cold, so they can also say that they have a bad cold about the margin. If you explicitly express what you need to answer (provide suggestions, send a code, check your patch or other), it is most likely to get useful answers. This will give a maximum of time and energy, which makes it easy to get to help you.
Solve your problem, the less time you need, the more you can take an answer from a busy expert port. Therefore, the structure of the optimization problem is minimized, and the experts will have a lot of help - this usual and simplified issues are different. So, ask "I want to know better X, can I give some hints?" I usually ask "Can you explain X?" Better. If your code can't work, ask what is wrong, than you ask others to make much more attention. Don't ask questions that should be solved by yourself.
These issues have to be done by you, you will learn from the middle. You can ask for a prompt and suggestions, but do not request a complete solution.
Remove meaningless questions
Don't use meaningless words to end your questions, for example, "Can someone help me?" Or "Is there an answer?" "No people do?".
First of all: If you are not very suitable for the description of the problem, this is more painted. Second: Because this question is to draw a snake, others will be tired of you - and usually use logically correct answers to represent their contempt, for example: "Yes, someone can help you" or "no, no answer".
Humility is not harmful, and often help
Gift, use "please" and "thank you very much." Let everyone know that you spend time obligations to help heart gratitude. Also, if you have a lot of problems, you can't solve it, and the courtesy will increase your opportunity to get useful answers.
After the problem is solved, add a short description
After the problem is resolved, send someone to all people who have helped you, let them know how the problem is solved, and once again expressed gratitude. If the problem has attracted extensive attention in the newsgroup or mailing list, there should be a supplementary instructions there. Supplementation does not have to be long or deep; simple sentence "Thank you, upstairs, try it tonight." "Hello, it is the network cable! Thank you!" More than anything else. In fact, unless the conclusion is really technical, short and lovely summary is better than a long academic papers. Explain how the problem is solved, but it is not necessary to repeat the process of solving the problem.
In addition to representing politeness and feedback, this supplement helps others in the mailing list / newsgroup / forum to search for your full solution to you, which may also be useful to them. This supplement helps all people who have provided help from it. This feeling is very important for those tutors or experts you have to help them.
In addition, please post it, when you are resolved, please give a batch according to the value of the answer, the score will give the resolution to the answer that most emphasizes your problem, which can drive the enthusiasm of the answer, reflect the labor value of the restriction Instead, regardless of the average distribution score, the problem will be discouraged; good people have good news, satisfy their desire, you will taste the sweetness when you post new questions.
