The wisdom of questioning
Copyright (C) 2001 by Eric S. Raymond
Chinese version copyleft 2001 by D.h.grand (Nobody/ginux)
English version: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Thanks to Eric's patient guidance and consent, this article was completed and published, this guide
The English version of the copyright for Eric Steven Raymond all,
Chinese version of Copyright by D.h.grand[nobody/ginux] all.
In the hacker world, what kind of answer can you get when you ask a technical question? It depends on digging.
The difficulty of the answer is also determined by the way you ask questions. This guide is designed to help you improve your questioning skills to
Get the answers you want most.
First you have to understand that hackers have a preference for tough tasks or good questions that can motivate 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 encouragement, a gift, can improve our comprehension, and usually
Exposes problems that we have never realized or thought about before. For hackers and
Say, "well asked!" "It's a heartfelt compliment.
Although hackers have a bad reputation for contempt for simple problems and unfriendly, sometimes it seems as if we are new to newbies,
Hostile to knowledge-poor people, but not in fact.
We don't want to hide the contempt for such people-they don't want to think, or they don't do it before they ask questions.
What they should do. These people only kill time--they just take it, they never give it, they burn me for nothing.
Time, and we could have spent the time on more interesting questions or more deserving people to answer.
We call this man "loser" (for historical reasons, we sometimes
Spell it "Lusers").
We are largely volunteers, taking time out of busy life to answer questions, and often
Be overwhelmed by questions. So we're relentlessly filtering out some of the topics, especially those that look like losers.
The guy 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. I
We didn't ask you to give in to us--in fact, most of us like fair trade, but
, as long as you make a small effort to meet the minimum requirements, we will welcome you to join our
Culture. But let us help those who do not want to help themselves is not
Meaning. If you can't accept this kind of "discrimination," we suggest you spend some money to find a business company to sign
Technical support agreement come on, don't beg for help from hackers.
If you decide to turn to us for help, you certainly don't want to be seen as a loser, but rather as a loser.
Rapporteur The best way to get effective answers right away is to ask questions like winners--smart, confident,
The idea of solving a problem is only occasionally needed to get a little help on a particular issue.
(Welcome suggestions for improvements to this guide.) Any advice please e-mail to esr@thyrsus.com, however
Please note that this article is not a general guide to network etiquette, and I usually refuse to be helpful in the technical forum
Suggestions for useful answers. ）
(Of course, if you write Chinese, you'd better send it to dhgrand@hotmail.com;-)
========
Before you 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 set you
Image: You are not a vain beggar, unwilling to waste other people's time. If asked
Who can learn from the answers, we are more than happy to answer his questions.
Thoughtful thinking, ready for your problems, hasty questions can only be hastily answered, or simply
Less than any answer. The more you are trying to solve a problem before you ask for help, the more you can get real
The quality of the help.
Be careful not to ask the wrong questions. If your problem is based on the wrong assumptions, ordinary hackers (J. Random
Hacker) usually answers you with meaningless literal explanations, thinking "stupid questions ...", Nozomi.
Look at your lessons from the answer to the question (not the answer you want to get).
Never assume that you are qualified for the answer. After all, you don't pay for this service.
compensation. You have to "earn" yourself an answer by proposing a content, interesting, thinking
The problem of dimensional motivation--a problem that has a potential contribution to the experience of the community, not just the passive
Ask 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? "Well" I should check what
Place? It's easier to get a response than to put the exact process on the list. Because you look as if you have
By pointing the right direction, you have the ability and determination to accomplish it.
========
How to ask questions
========
------------
Select Forum Carefully
------------
Be careful to choose the occasion to ask questions. If, as described below, you are likely to be overlooked or seen as a loser:
1. Post your question in a irrelevant forum
2. Post very elementary questions in forums that explore advanced techniques;
3. Cross-posting in too many different newsgroups
----------------------------
Use your words properly, correct your grammar, and spell them correctly.
----------------------------
We find from experience that careless writers are often sloppy thinkers (I dare to pack tickets).
It is not worth answering the careless question, we prefer to spend it elsewhere.
Correct spelling, punctuation, and capitalization are important.
More generally, if your question is written like a functional illiteracy, you are likely to be overlooked.
If you're asking questions in a non-native language forum, you can make a few spelling and grammatical mistakes--but never
Thinking about the tiger (yes, we can figure out the difference)
----------------------------
Use meaning rich, descriptive accurate title
----------------------------
In a mailing list or newsgroup, about 50 words in the title of the topic is to seize the attention of senior experts
The golden opportunity. Don't use chattering "help" (not to mention "HELP"!!!!! "This
Disgusting) to waste the opportunity. Don't try to impress us with your pain,
Do not use spaces instead of the description of the problem, even if it is a very brief description.
Stupid question:
Help me! My laptop is not showing up properly!
Smart questions:
XFREE86 4.1 mouse cursor deformation, fooware MV1005 of the display chip.
If you ask a question in the reply, remember to revise the content title to indicate that there is a problem. One
Problems that look like "Re: Test" or "Re: New Bug" are hard to draw enough attention to. In addition, the introduction
Use and prune the contents of the previous article to leave clues to the new reader.
------------------
Accurate description, large amount of information
------------------
1. Carefully and clearly describe the symptoms.
2. Provide the environment in which the problem occurred (machine configuration, operating system, application, and other).
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.
Try to imagine how a hacker would ask you to give him an answer in advance of a question.
Simon Tatham wrote an excellent essay titled "How to Report a bug effectively". Strongly recommend you also read it.
--------
Not many words.
--------
You need to provide accurate and effective information. This is not to ask you to simply put tons of error codes or data out
The full dump is excerpted into your question. If you have a large and complex test condition, try to cut it as small as possible.
The better.
The use of this is at least three points. First, show that you have worked hard to simplify the problem, which can make you
The opportunity to answer increases; second, the chance of simplifying the problem to get a useful answer increases; third, in refining
In the process of your bug report, you may be able to find out where the problem is or make corrections yourself.
------------------
Just a symptom, not a guess.
------------------
Tell the hackers what you think the problem is, and it doesn't help. (If your inference is so effective, use
Ask someone for help? ), so be sure that you tell them the symptoms of the problem, and do not add your own
Understanding and inference of their own. Let the hackers diagnose it.
Stupid question:
I encountered SIG11 errors again and again in kernel compilation, and I suspect that one of the flying lines is on the motherboard's route,
What should be the best way to check this situation?
Smart questions:
My homemade set of k6/233 systems, Motherboard is fic-pa2007 (VIA Apollo VP2 chipset), 256MB
Corsair PC133
SDRAM, in the kernel compile frequently produces SIG11 error, from the boot 20 minutes after this situation, boot
Never happened in the first 20 minutes. Restarting is not a good use, but the shutdown will work 20 minutes a night. All
Memory has been changed, no effect. The typical compilation record for the relevant section is as follows ....
------------------
List symptoms in chronological order
------------------
The most helpful clue to finding a problem is often a series of actions before the problem occurs, so your instructions
Should contain the operation steps, as well as the computer's reaction until the problem arises.
If your instructions are long (more than four paragraphs), it will be helpful to brief the questions at the beginning, and then on time
The order is detailed. So hackers know what to look for in your notes.
http://www.bkjia.com/PHPjc/313920.html www.bkjia.com true http://www.bkjia.com/PHPjc/313920.html techarticle The wisdom of questioning (C) 2001 by Eric S. Raymond Chinese version copyleft 2001 by D.h.grand (Nobody/ginux) English version: HTTP://WWW.TUXEDO.ORG/~ESR /faqs/smart-questions.html thanks to Eric's ...
