This article is now modified for the specific situation of the programmer home, I hope everyone will make their own opinions and suggestions. . .
Ask the wisdom
Copyright (c) 2001 by Eric S. raymond Chinese version COPYLEFT 2001 by DHGRAND (Nobody / Ginux) English: http://www.tuxedo.org/~esr/faqs/smart-questions.html Thanks to ERIC Patience Guide And agree, this article can be completed and released, this guide English copyright is Eric Steven raymond, the Chinese version is copyrighted by DHGRAND [NoBody / Ginux]. CCF modified version of the copyright is owned by the CCF Forum.
In the technology world, what kind of answer can you get when a technical issue is proposed? This depends on the difficulty of digging out the answer, also depends on the method you ask. This guide is intended to help you improve your skills to get your most wanted answer.
First of all, you must understand that the masters of the forum generally prefer the arduous tasks, or can inspire their thinking. If so, do we come back? If you have a good question worthy of we repeatedly chew, we will be grateful to you. A good problem is that incentives, it is a thick gift, which can improve our understanding, and usually expose what we have never realized or thinking. For the masters, "asking!" Is a strong praise from the heart.
Although the masters have despise simple questions and unsolic bad names, sometimes it seems that we have hostile to new hands, and have hostile to knowledge, but it is not that. We don't want to cover some people's contempt - they don't want to think, or don't complete what they should do before you ask. This kind of person will only murder - they are only willing to request, never pay, endlessly consume us, and we can use time to use the more interesting questions or more worth answering. We call such artificially "losers" (due to historical reasons, we sometimes spell "lusers").
We are largely belonging to
Volunteers, take the time from the busy life to solve the Q & A, and often being submerged. So we have ruthlessly filter out some topics, especially those who look like a loser, so that more efficient use of time to answer the victory.
If you think that we are too arrogant, let you not cool, let you blame, you may wish to think about it. We don't ask you to ask questions - in fact, most people in our favorite are all right, as long as you pay small efforts to do the most basic requirements, we will welcome your questions. But let us help those who are unwilling to help their self.
meaningful. If you can't accept this "discrimination", we recommend that you spend money to find a business company to sign a technical support protocol, don't give help to the technical master of the obligation.
If you decide to help us, of course, I don't want to be considered a loser, and I don't want to be a member of the loser. The best way to get a valid answer is to ask questions like winners - smart, self-confidence, and solve problems, just occasionally need to get a little help on specific issues.
======== [Before Question] ========
Before you ask for technical issues to this forum, check you if you have:
1. Read the technical documentation and try to find answers.
2. Look in the answer in FAQ (a well-maintained FAQ can include :).
3. Search online (personal recommendation google ~~~).
When you ask questions, you must first explain what you have before, don't ask those answers that can be found directly from the document, because the master should not always go to check the document, your problem should be concentrated to the document The problem of experience! Pay attention to establish your image: You are not a beggar who is in vicalation, I don't want to waste others. This also allows you to see your efforts and the attempts, from many aspects to simplify others attempt to solve the problem. If the questioner can learn something from the answer, we are 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 you seek help, you can get substantive help.
Be careful, don't ask questions. If your problem is based on the wrong assumption, the ordinary hacker (J. Random Hacker usually uses meaningless literal explanation to reply you, thinking "stupid problems ...", I hope you will answer from the question (and Did you you want to get a lesson. There are many people who have seen too many stupid problems will definitely change the anger and use cold whey way to combat you, and even more swearing. .
Never think of being qualified to get answers, you don't have this eligibility. After all, you didn't pay any remuneration for this service. You have to go back to "earn" back to an answer, relying on a question of connotation, interesting, thinking incentive effect - a problem with potential contribution to the community, not just passive from others Knowledge - to earn this answer.
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 your ability and determination.
======== [How to ask] ========
----------------
[Care to choose forum]
----------------
Carefully choose to ask questions. If you are likely to be described below, you are likely to be ignored or as a loser:
1. Issues in the forum in the wind horse
2. In the discussion of advanced skills, it posted very primary questions;
3. A patch is strictly forbidden
----------------------------
[Use the speck, the grammat is correct, spelling correct]
----------------------------
We found out from experience, careful writers are often horses and tigers (I dare to make package). Carefully describe the environment of your problem, and the time, number of times, etc., the accurate paste error message, all of which are the necessary help you get the answer, answer the problem of careless people is not worth it, we would rather spend time elsewhere.
Correct spelling, punctuation and case is important. More general, if your question is written like a half illiteracy, you are likely to be ignored.
----------------------------
[Use rich use, describe accurate title]
----------------------------
In the forum, the clear theme title within about 20 words with classification is to grasp the prime time of the master's attention. Don't use your chatter "helping" (let alone "save !! !!!" This is a dissentful word) to waste this opportunity. Don't want to use your pain to touch us, don't use space instead of the description of the problem, even if it is an extremely short description. Quote:
Stupid question: Help! My lap is not displayed normally! Smart problems: Xfree86 4.1 Lower mouse cursor deformed, FooWare MV1005 display chip.
------------------
[Accurate description, large amount of information]
------------------
1. Carefully describe the symptoms.
2. Provide a problem that occurs (machine configuration, operating system, application, and other).
3. Explain how you study and understand this problem before you ask questions.
4. Note What steps you have taken before you ask questions.
5. Russen has recently made hardware, software changes that may have an impact.
Try to see how a master will ask you, give him an answer when you ask questions.
Simon Tatham wrote an excellent essay called "How to Effective Report Bug". Strongly recommend you to read it.
------------
[Words are not there]
------------
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.
------------------
[Just say symptoms, don't talk about guess]
------------------
Tell the masters, what you think is, how is it caused? (If your inferior is so effective, do you want to help others?), So be sure that you originally tell the symptoms of their questions, don't add your own understanding and presentation. Let masters to diagnose.
Quote:
Stupid question: I encountered a SIG11 error in the kernel compilation, I suspect that a flying line is on the front line of the motherboard, how should this be the best? Clever problem: I have a set of K6 / 233 systems, motherboards are FIC-PA2007 (VIA Apollo VP2 chipset), 256MB Corsair PC133 SDRAM, frequently generating SIG11 errors in kernel compilation, from booting 20 minutes later, this situation I never happen within 20 minutes before booting. It is useless to restart, but it will work 20 minutes in one night. All memory has changed, no effect. Typical compilation records in the relevant part ....
[qutoe]
Stupid question:
My ASP program suddenly doesn't work? help
Smart problem:
When I started debugging the ASP program today, the error message is "" You don't have enough permissions to perform this file operation, error code 0x0008045, in row 45 ", I have searched MSDN, the reason for the error may occur, I have already checked it. But did not understand why, the line 45 program is like this. . My environment is W IIN2000 Server, IIS5, NTFS file system, the source program of this program is as follows. .
[/ quote] ------------------
[Symptoms in time sequence]
------------------ A series of operations before identifying the problem, often is a series of operations before the problem, so your instructions should include steps, as well as your computer The reaction until the problem is generated.
If your description is long (more than four paragraphs), the problem will help, followed by the time order. This hacker knows what to find in your instructions.
