2016.10.22 来源：How To Ask Questions The Smart Way (原文网页) Eric Steven Raymond
第一部分 要用清晰的、语法正确和拼写正确的语言
1. 写作不仔细的人在思维和写代码方面也有这样的问题。
2. 把问题说清楚，用正式准确的语言。
3. 注意拼写，强调和大写问题。全大写比较粗鲁不礼貌，全小写可读性差。
4. 不要像个半文盲，你喜欢用缩写的话，别人就不大可能回复你。
5. 如果英语不是母语，可以提前声明，文中有例句可参考。
第二部分 不要表现得像个loser
1. 不论什么情况，不要抱怨、攻击、威胁。
2. 别人在公共场合批评你，不要坚持让他发私人邮件，也不要在论坛里说你被谁私下攻击了。
3. 友好和有用，选择一个。
4. 别人可能也会攻击你，即使你没什么错，这种情况不要抱怨，他们可能自以为是专家。或者他们自以为是心理学家，就看你是不是会搞砸。
英文原文：879字
Write in clear, grammatical, correctly-spelled language
We've found by experience that people who are careless and sloppy writers are usually also careless and sloppy at thinking and coding (often enough to bet on, anyway). Answering questions for careless and sloppy thinkers is not rewarding; we'd rather spend our time elsewhere.
So expressing your question clearly and well is important. If you can't be bothered to do that, we can't be bothered to pay attention. Spend the extra effort to polish your language. It doesn't have to be stiff or formal — in fact, hacker culture values informal, slangy and humorous language used with precision. But it has tobeprecise; there has to be some indication that you're thinking and paying attention.
Spell, punctuate, and capitalize correctly. Don't confuse“its”with“it's”,“loose”with“lose”, or“discrete”with“discreet”. Don't TYPE IN ALL CAPS; this is read as shouting and considered rude. (All-smalls is only slightly less annoying, as it's difficult to read. Alan Cox can get away with it, but you can't.)
More generally, if you write like a semi-literate boob you will very likely be ignored. So don't use instant-messaging shortcuts. Spelling "you" as "u" makes you look like a semi-literate boob to save two entire keystrokes. Worse: writing like a l33t script kiddie hax0r is the absolute kiss of death and guarantees you will receive nothing but stony silence (or, at best, a heaping helping of scorn and sarcasm) in return.
If you are asking questions in a forum that does not use your native language, you will get a limited amount of slack for spelling and grammar errors — but no extra slack at all for laziness (and yes, we can usually spot that difference). Also, unless you know what your respondent's languages are, write in English. Busy hackers tend to simply flush questions in languages they don't understand, and English is the working language of the Internet. By writing in English you minimize your chances that your question will be discarded unread.
If you are writing in English but it is a second language for you, it is good form to alert potential respondents to potential language difficulties and options for getting around them. Examples:
English is not my native language; please excuse typing errors.
If you speak $LANGUAGE, please email/PM me; I may need assistance translating my question.
I am familiar with the technical terms, but some slang expressions and idioms are difficult for me.
I've posted my question in $LANGUAGE and English. I'll be glad to translate responses, if you only use one or the other.
On Not Reacting Like A Loser
Odds are you'll screw up a few times on hacker community forums — in ways detailed in this article, or similar. And you'll be told exactly how you screwed up, possibly with colourful asides. In public.
When this happens, the worst thing you can do is whine about the experience, claim to have been verbally assaulted, demand apologies, scream, hold your breath, threaten lawsuits, complain to people's employers, leave the toilet seat up, etc. Instead, here's what you do:
Get over it. It's normal. In fact, it's healthy and appropriate.
Community standards do not maintain themselves: They're maintained by people actively applying them, visibly,in public. Don't whine that all criticism should have been conveyed via private e-mail: That's not how it works. Nor is it useful to insist you've been personally insulted when someone comments that one of your claims was wrong, or that his views differ. Those are loser attitudes.
There have been hacker forums where, out of some misguided sense of hyper-courtesy, participants are banned from posting any fault-finding with another's posts, and told“Don't say anything if you're unwilling to help the user.”The resulting departure of clueful participants to elsewhere causes them to descend into meaningless babble and become useless as technical forums.
Exaggeratedly“friendly”(in that fashion) or useful: Pick one.
Remember: When that hacker tells you that you've screwed up, and (no matter how gruffly) tells you not to do it again, he's acting out of concern for (1) you and (2) his community. It would be much easier for him to ignore you and filter you out of his life. If you can't manage to be grateful, at least have a little dignity, don't whine, and don't expect to be treated like a fragile doll just because you're a newcomer with a theatrically hypersensitive soul and delusions of entitlement.
Sometimes people will attack you personally, flame without an apparent reason, etc., even if you don't screw up (or have only screwed up in their imagination). In this case, complaining is the way toreallyscrew up.
These flamers are either lamers who don't have a clue but believe themselves to be experts, or would-be psychologists testing whether you'll screw up. The other readers either ignore them, or find ways to deal with them on their own. The flamers' behavior creates problems for themselves, which don't have to concern you.
Don't let yourself be drawn into a flamewar, either. Most flames are best ignored — after you've checked whether they are really flames, not pointers to the ways in which you have screwed up, and not cleverly ciphered answers to your real question (this happens as well).
本文中文259字，阅读和翻译要点耗时40min。
网友评论