This link has been bookmarked by 590 people . It was first bookmarked on 02 Mar 2006, by Jon Phipps.
-
22 Jun 25
-
05 Mar 23
hideo isHow To Ask Questions The Smart Way
Translations: Brazilo-Portuguese Chinese (Traditional) Czech Dutch Estonian French Georgian German Greek Hindi Hungarian Indonesion Japanese Lithuanian Polish Portuguese Russian Spanish Ukrainian Uzbek If you want… -
05 Feb 19
flyingpuddingIn the world of hackers, the kind of answers you get to your technical questions depends as much on the way you ask the questions as on the difficulty of developing the answer. This guide will teach you how to ask questions in a way more likely to get you a satisfactory answer.
Now that use of open source has become widespread, you can often get as good answers from other, more experienced users as from hackers. This is a Good Thing; users tend to be just a little bit more tolerant of the kind of failures newbies often have. Still, treating experienced users like hackers in the ways we recommend here will generally be the most effective way to get useful answers out of them, too. -
25 Jul 18
-
07 May 18
-
18 Jun 17
-
14 Apr 17
-
What we are, unapologetically, is hostile to people who seem to be unwilling to think or to do their own homework before asking questions. People like that are time sinks — they take without giving back, and they waste time we could have spent on another question more interesting and another person more worthy of an answer.
-
We like answering questions for people who have demonstrated they can learn from the answers.
-
Search, then ask on Stack Exchange
-
-
01 Apr 17
-
We like answering questions for people who have demonstrated they can learn from the answers.
-
Do not expect to be able to solve a complicated problem with a few seconds of Googling.
-
Don't shotgun-blast all the available help channels at once, that's like yelling and irritates people. Step through them softly.
-
One good convention for subject headers, used by many tech support organizations, is “object - deviation”. The “object” part specifies what thing or group of things is having a problem, and the “deviation” part describes the deviation from expected behavior.
-
If you can't be bothered to do that, we can't be bothered to pay attention.
-
Data should be included as-is, so respondents can have confidence that they are seeing what you saw.
-
Play it so the maintainers will want to apologize to you if the bug is real, rather than so that you will owe them an apology if you have messed up.
-
The smaller your minimal test case is, the better
-
It is OK to ask for hints, but not for entire solutions.
-
he person who sent it thinks you should have Searched The Fucking Web.
-
(If this puzzles you, remember that we value a question by what it teaches us.)
-
Answering one good question is like feeding a hungry person one meal, but teaching them research skills by example is showing them how to grow food for a lifetime.
-
-
01 Jan 17
Yee Sian NgMany project websites link to this document in their sections on how to get help. That's fine, it's the use we intended — but if you are a webmaster creating such a link for your project page, please display prominently near the link notice that we …
-
11 Oct 16
-
23 Sep 16
-
We have learned the hard way that without such a notice, we will repeatedly be pestered by idiots who think having published this document makes it our job to solve all the world's technical problems.
-
-
15 Jul 16
-
07 Sep 15
-
25 Aug 15
-
08 Jul 15
-
13 Apr 15
-
15 Mar 15
-
04 Jan 15
-
03 Dec 14
-
02 Sep 14
-
06 Feb 14
-
26 Jan 14
Joelle Nebbe-Mornod"When you ask your question, display the fact that you have done these things first; this will help establish that you're not being a lazy sponge and wasting people's time. Better yet, display what you have learned from doing these things. We like answering questions for people who have demonstrated they can learn from the answers."
-
01 Jan 14
-
20 Dec 13
-
the kind of attitude that leads to competence — alert, thoughtful, observant, willing to be an active partner in developing a solution
-
RTFM and STFW
-
-
07 Dec 13
-
21 Oct 13
-
31 Aug 13
-
30 Jul 13
-
14 Jul 13
-
15 Jun 13
-
05 Jun 13
Sergey SergeevПочти правила поведения в интернетах. Как правильно задавать вопросы: http://t.co/zRKGJMM5
-
08 May 13
-
18 Dec 12
-
14 Nov 12
-
10 Oct 12
-
25 Sep 12
-
23 Aug 12
-
20 Aug 12
-
Instead, present the background facts and your question as clearly as you can. That is a better way to position yourself than by grovelling.
-
Don't waste your time, or ours, on crude primate politics
-
If you feel you do have a newbie question, just go there. But don't grovel there either.
-
-
01 Aug 12
Graham Perrinhttps://forums.FreeBSD.org/threads/error-message-when-booting-usb_err_timeout-ignored.63986/post-371519
-
05 Jul 12
-
04 Jul 12
-
25 Jun 12
-
20 Jun 12
-
25 May 12
-
16 May 12
-
10 May 12
-
21 Apr 12
-
16 Apr 12
-
04 Mar 12
-
27 Feb 12
-
07 Feb 12
-
16 Nov 11
-
06 Oct 11
-
28 Sep 11
-
21 Sep 11
-
20 Aug 11
-
15 Aug 11
-
13 Aug 11
-
11 Aug 11
-
03 Aug 11
-
28 Jul 11
-
01 Jul 11
Zoran RegvartIn the world of hackers, the kind of answers you get to your technical questions depends as much on the way you ask the questions as on the difficulty of developing the answer. This guide will teach you how to ask questions in a way more likely to get you a satisfactory answer.
-
29 Jun 11
Sascha Khttp://t.co/X1MxeqP is ja essentielle Medienkompentenz und sollte Grundschullehrstoff sein. Aber mich fragt ja keiner.
-
15 Jun 11
-
28 May 11
-
27 May 11
Leorg GnonMany project websites link to this document in their sections on how to get help . ...... for help with semantically-null questions like Can anyone help me? ..... Stupid: I'm having problems with my motherboard. Can anybody help? ...
-
23 May 11
-
20 May 11
-
10 May 11
-
06 May 11
-
02 May 11
Jeff BrazeeHow to ask smart questions (technically oriented).
-
27 Apr 11
-
19 Apr 11
-
21 Mar 11
yaakovfCopyright © 2001,2006 Eric S. Raymond, Rick Moen
reference Community documentation Forum Internet Links linux productivity Quick_Answers Reading software tips tutorials
-
01 Mar 11
-
27 Feb 11
-
24 Feb 11
-
15 Feb 11
-
25 Jan 11
Rebecca Martinhow to ask smart questions
-
22 Jan 11
-
28 Dec 10
-
21 Dec 10
-
07 Dec 10
-
28 Nov 10
-
26 Nov 10
-
26 Oct 10
-
04 Oct 10
-
Try to find an answer by searching the archives of the forum you plan to post to.
Try to find an answer by searching the Web.
Try to find an answer by reading the manual.
Try to find an answer by reading a FAQ.
Try to find an answer by inspection or experimentation.
Try to find an answer by asking a skilled friend.
If you're a programmer, try to find an answer by reading the source code.
-
Try to find an answer by searching the archives of the forum you plan to post to.
-
When you ask your question, display the fact that you have done these things first; this will help establish that you're not being a lazy sponge and wasting people's time.
-
In fact, it's a very good idea to do a keyword search for words relating to your problem on the newsgroup or mailing list archives before you post. It may find you an answer, and if not it will help you formulate a better question.
-
Read some of the back traffic before posting so you'll get a feel for how things are done there.
-
There is an increasing tendency for projects to do user support over a Web forum or IRC channel, with e-mail reserved more for development traffic. So look for those channels first when seeking project-specific help.
-
One good convention for subject headers, used by many tech support organizations, is “object - deviation”. The “object” part specifies what thing or group of things is having a problem, and the “deviation” part describes the deviation from expected behavior.
-
Send plain text mail, not HTML.
-
Don't send e-mail in which entire paragraphs are single multiply-wrapped lines. (This makes it too difficult to reply to just part of the message.) Assume that your respondents will be reading mail on 80-character-wide text displays and set your line wrap accordingly, to something less than 80.
-
Describe the symptoms of your problem or bug carefully and clearly.
-
Describe the environment in which it occurs
-
Describe the research you did to try and understand the problem before you asked the question.
-
Describe the diagnostic steps you took to try and pin down the problem yourself before you asked the question.
-
It's not useful to tell hackers what you think is causing your problem.
-
Often, people who need technical help have a high-level goal in mind and get stuck on what they think is one particular path towards the goal. They come for help with the step, but don't realize that the path is wrong. It can take substantial effort to get past this.
-
Send a note after the problem has been solved to all who helped you; let them know how it came out and thank them again for their help. If the problem attracted general interest in a mailing list or newsgroup, it's appropriate to post the followup there.
-
Besides being courteous and informative, this sort of followup will help others searching the archive of the mailing-list/newsgroup/forum to know exactly which solution helped you and thus may also help them.
-
-
29 Sep 10
-
20 Aug 10
-
13 Aug 10
-
07 Aug 10
-
18 Jul 10
-
28 Jun 10
-
20 Jun 10
-
17 Jun 10
-
10 Jun 10
-
02 Jun 10
-
26 May 10
-
08 Apr 10
Page Comments
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.