Although this is the old stereotype, but the latest answer the questions in the process of, a little touch, your good questions, ask the accurate, to answer your talents motivated to give you a reply, so that you can quickly solve your problem, a lot of people don't know how to ask questions, so I'm going to put this old article turned set-top, take time to look at,
If no time, at least look at the picture below:
=================================================================================
When a technical question, how can you get the answer? Depending on the difficulty of digging out the answer, also depends on the way you ask questions, this guide is intended to help you improve your questioning skills, in order to get the answer you want...
Don't want to hide a contempt for such some - they are reluctant to think, or not to complete them before asking should do , this kind of person will only be murder time - they only want to ask for, never pay, irrational use of our time, and we could have used his time in the more interesting question or to answer, we call such people "losers" (due to historical reasons, we sometimes spell it as "lusers"),
Questions Before (Before You Ask)
In via email, newsgroups, or chat room put forward technical problems before, check you have do it:
1. Read through the manual, and try to find their own answers,
2. To find the answer in the FAQ, a FAQ can maintain well everything:),
3. Search on the Internet (personally recommend Google ~ ~ ~),
4. Ask at that friends around you,
When you ask questions, the first to say what did you do before this; This will help to set up your image: you are not a run from the unearned beggars, don't like to waste other people's time, if the questioner can learn from the answer, we are more willing to answer his question,
comprehensive thinking, ready for your question, hasty questions get hasty answers, or don't get any answer, more show before seeking help efforts to solve the problem, the more you can get substantial help,
Be careful not to ask a wrong question,
On the other hand, it shows that you are willing to do something in the process of looking for the answer, is a very good start, "who can give me some tips?" , "what am I missing from this example?" And "where should I check?" Than "please stick the exact process out" are more likely to get a reply, because you appear as long as someone in the right direction, you will have to complete its ability and determination,
How to Ask questions (When You Ask)
Carefully chosen BBS
Careful choice questions, if as described below, you are likely to be ignored or is considered a failure:
1. In the different phase and BBS posted for you
2. To explore advanced techniques of BBS posted very primary problem; Vice versa
3. In too many different cross Posting to newsgroups
Apt of terms, grammatically correct, spelling,
From experience, we found that the careless writers are often sloppy thinkers (I'm sure),
Answer the carelessness of the question is not worth, we would rather waste time elsewhere,
The correct spelling, punctuation and capitalization is very important,
More generally, if you write questions like a semi-literate, you are likely to be ignored,
If you're using the mother tongue of BBS to ask questions, you can make some small mistakes on spelling and grammar, but must not be careless on thinking (yes, we can find out the two respectively)
Use the rich meanings, describe accurately the title of the
In the mailing list or newsgroup, about 50 words within the theme of the title is the golden time to hold senior experts attention, don't use chatter of "help" (not to mention "help!!!!!!!!!!! "Such a repulsive) to waste this opportunity, do not use your painful to impress us, don't use Spaces instead of the description of the problem, even if extremely short description,
Stupid question:
Help! My laptop can't display properly!
Smart question:
XFree86 4.1 under the mouse cursor deformation, Fooware MV1005 display chip,
If you in reply to questions, remember to modify the content title, shows that there is a problem, a look like "Re: test" or "Re: new bug" problem is very difficult to cause enough attention, in addition, reference and reducing the content of the above, leaving the new readers clues,
Accurate description, informative
1. Clear describe the problem carefully,
2. The problems of environment (machine configuration, operating systems, applications, and anything else),
3. Before you ask how to study and understand the problem,
4. Before you ask what the steps to solve it,
5. List recently done anything may have affected the hardware, software change,
Simon Tatham wrote an article called "how to effectively report bugs" excellent essays, strongly recommend you read it,
Words are not much
you need to provide accurate and effective information, this is not to ask you to simply put a ton of error code or data dump excerpts completely to your questions, if you have a large and complex test conditions, try to cut it as small as possible,
Do use at least three, first, show that you made an effort to simplify the problem, the chance of this can make you get the answer; Second, to simplify the problem make you the opportunity to get useful answers increases; Third, in the process of refining your bug reports, maybe you can find out the problem or to make correction,
Stupid question:
I in the kernel compilation to meet SIG11 wrong again and again, I doubt for a jumper wire on the main board of going online,
This kind of situation should be how to check the best?
Smart question:
My homemade a K6/233 system, motherboard is FIC - PA2007 (VIA Apollo VP2 chipset), 256 MB
Corsair PC133 SDRAM, SIG11 error occurred frequently in kernel compilation, the boot after 20 minutes to have this kind of situation, never happened, 20 minutes before starting the restart is useless, but turned off and can work in an evening for 20 minutes, all memory are changed, no effect, the relevant part of the typical compile record as follows... ,
Symptoms are listed in chronological order
To find out the problem of the most helpful clues, is usually a series of problem before operation, therefore, your description should include steps, and the reaction of the computer, until the problem arise,
If you have a very long (more than four paragraphs), in brief questions will help in the beginning, the following details in chronological order, this can let a person know what in your notes,
Understand what you want to ask
Rambling questions almost endless time black hole, the most can give you useful answers is also the busiest people (they busy because they want to do most of the work themselves), such people can unrestrained time black hole is not too cold, so they can say the rambling questions is not a cold, if you need clear what respondents (advice, sending a piece of code, check your patches or other), they are most likely to get useful answers, this will set a limit of time and energy, facilitate respondents focus on to help you, this is work,
The less time you need to solve your problem, can take out the answer is from busy experts, as a result, the structure of the optimization problem, the time required to minimize experts to solve it, there will be a big help - this usually and simplify the problem, therefore, ask, "I want to a better understanding of X, can give some tips?" Often than asking "can you explain X?" Better, if your code doesn't work, ask it what's wrong, is much more sensible than asking others to change for you,
don't ask should solve problems
Is for you to solve these problems, you can learn something from it, you can ask to give some hints, but don't ask for a complete solution,
Get rid of the meaningless questions
Don't end with meaningless words to ask questions, such as "can someone help me?" Or have the answer? "" ,
First: if you are a description of the problem is not very appropriate, so ask more gild the lily, and second, because asked is gild the lily, you are very boring - and often use logically correct answer to show their contempt, for example: "yes, someone can help you" or "no, not the answer,"
Absolutely no harm, modesty and often helps a lot
Polite, multi-purpose "please" and "first to say" thanks ", let everyone know you spend time obligations to help grateful to them,
However, if you have a lot of problems cannot be solved, polite will increases your chance to get useful answers,
after the problem solving, add a brief description
Problem solving, to all the people who helped you send a, let them know what the problem is how to solve, and to thank them again, if the problem has caused wide public concern in the newsgroup or mailing list, there should be a supplement, added that don't have to be very long or very deep; Simple sentence "how are you, originally is the cable out of the question! Thank you, Bill "better than nothing, in fact, unless the conclusion really have technical content, or short lovely summary is better than long academic papers, explain the question is how to solve, but don't have the process to solve the problem repeat again,
In addition to the politeness and feedback information, this supplement will help others in the mailing list/newsgroup/BBS search can help you have a complete solution, this may is also useful to them,
The last (at least)? , this supplement will help all the people who have helped get satisfaction, this kind of feeling for those you seek help from their teacher or expert, is very important, concerns persist can let a person lose heart; Good people good, meet their desire, you will be in the next post new taste,
the last problem solving, to stick to?
CodePudding user response:
all in all, hope everyone can perfectly solve the problem, also hope that we can learn want to learn in the BBS.CodePudding user response:
Thank you for handling, very meaningfulCodePudding user response:
Shi Xiong attentively theCodePudding user response:
Met some people have problems is also no specific reason for the even directly to the code is oneself is small white nothing will not,,,CodePudding user response:
nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull