The wisdom of questioning, the question of wisdom, has to be reminded of how to deal with

"The wisdom of questioning, the question of wisdom" has to remind
The wisdom of questioning, the question of wisdom
This article changes from the "wisdom of asking questions" article, the copyright information see the article:

What kind of answer can you get when you ask a technical question? It depends on the difficulty of digging out the answer, and also on the way you ask. This guide is designed to help you improve your questioning skills to get the answers you want most.
First you have to understand that we prefer a difficult task or a good question that inspires them to think. If not, what are we going to do? If you have a good question that deserves our repeated chewing and pondering, we will be grateful to you. The good question is that motivation, a gift, can improve our understanding and often exposes problems that we have never realized or thought about before. For us, "Good question!" "It's a heartfelt compliment.
We do not want to hide the contempt for such people-they do not want to think, or do not do what they should do before they ask questions. They only kill time-they just take it, never give it, and consume our time, and we can spend time with more interesting questions or more deserving people. We call this A "loser" (for historical reasons, we sometimes spell it "lusers").
We are largely volunteers, taking time out of busy life to answer questions, and often overwhelmed by questions. So we ruthlessly filter out some of the topics, especially those who look like losers, in order to use time more efficiently to answer the winner's question.
If you feel that we are too arrogant to make you uncomfortable, let you wronged, you might as well put yourself in your mind. We are not asking you to give in to us-in fact, most of us like fair trade, but if you make a small effort to meet the minimum requirements, we will welcome you to our culture. But it makes no sense for us to help those who are unwilling to help themselves. If you can't accept this kind of "discrimination," we suggest you spend some money looking for a business company to sign a technical support agreement.

Before ——— ask ———

Before you ask a technical question by email, newsgroup, or chat room, check to make sure you do:
1. Read through the manual and try to find the answer yourself.
2. Find the answer in the FAQ (a well-maintained FAQ can be all-encompassing:).
3. Search online (personal referral google~~~).
4. Ask your friends who are proficient in this way.
When you ask a question, the first thing you need to know is what you did before that, and it will help to build up your image: You are not a beggar who is trying to get something for nothing, and not willing to waste others ' time. If the questioner can learn something from the answer, we are more than happy to answer his question.
Thoughtful thinking, preparing your questions, hasty questions can only be answered hastily, or there is no answer at all. The more you show the effort to solve the problem before you ask for help, the more substantial help you can get.
Never assume that you are qualified for the answer. After all, you're not paying any compensation for this service. You have to "earn" your own answer by asking a meaningful, interesting, and stimulating question-a problem that has a potential contribution to the Community's experience, not just a passive request for knowledge from others-to earn the answer.
On the other hand, it is a very good start to show that you are willing to do something in the process of finding the answer. "Who can give a hint?" What is missing in my example? "and" Where should I check? " It's easier to get a response than to put the exact process on the list. Because you seem to have the ability and determination to do it as long as someone is pointing the right way.

——— How to ask ———

One, please carefully select the grouping, if as described below, you are likely to be ignored or considered a loser:
1. Post your question in a irrelevant forum
2. Post very elementary questions in forums that explore advanced techniques;
3. Posting in too many different newsgroups
Second, the use of meaning rich, descriptive accurate title:
In a mailing list or newsgroup, a topic title of about 50 words is the golden opportunity to capture the attention of a seasoned expert. Don't use chattering "help" (not to mention "HELP"!!!!! "It's disgusting" to waste this opportunity. Don't try to impress us with the extent of your pain, don't use spaces instead of the description of the problem, even if it's a very brief description.
Three, accurate description, the information is large:
1. Carefully and clearly describe the symptoms.
2. Provide the environment in which the problem occurred (machine configuration, * system, application, and anything else).
3. Explain how you study and understand the problem before you ask it.
4. Explain what steps you have taken before asking to solve it.
5. List recent hardware and software changes that may have impacted.
Four, the words are not more:
You need to provide accurate and effective information. This is not to ask you to simply extract tons of error codes or data from a full dump into your question. If you have a large and complex test condition, try to cut it as small as possible.
The use of this is at least three points. First, show that you have worked hard to simplify the problem, which can increase your chances of getting answers, and secondly, the opportunity to simplify your questions to get useful answers increases; Third, in the process of refining your bug report, you may be able to identify the problem or make corrections yourself.
V. List symptoms Chronologically:
The most helpful clue to finding a problem is often a series of * before the problem occurs, so your instructions should include * steps, and the computer's response, until the problem arises.
If your instructions are long (more than four paragraphs), it helps to outline the questions at the beginning, followed by chronological detail. So we'll know what to look for in your instructions.

Posted on @ August 26, 2004


This article from Csdn Blog, reproduced please indicate the source: http://blog.csdn.net/magus_yang/archive/2004/08/26/85579.aspx

------Solution--------------------
Asking questions sometimes really takes a mind
LZ to 1 points can be 3ks
------Solution--------------------
People who love brains also pay attention to the way they ask questions.
------Solution--------------------
Well,,,,, educated ....
------Solution--------------------
It's also a skill to ask.
------Solution--------------------
That's very good! By the way!
------Solution--------------------
This must be top
Often see asked questions on a word or a few words
Someone who needs an answer to a sentence guess in turn ask the person who asked the question
------Solution--------------------
I learned something.
------Solution--------------------
That's good.
------Solution--------------------
discuss

The boss has been here for more than 7 years. Bowed..

------Solution--------------------
Oh really so every time asked questions to analyze the problem and then tidy up so no matter ask or answer is good
------Solution--------------------
Teachable......
To despise the direct answer ...
Continue downstairs ...

