![]() ![]() Looks like we're reflexively rude to newbies and the ignorant. Questions with what looks like hostility or arrogance. Reveal problems we might not have noticed or thought about otherwise.Īmong hackers, “ Good question!” is a strong and sincereĭespite this, hackers have a reputation for meeting simple Good questions help us develop our understanding, and often To chew on we'll be grateful to you good questions are a stimulus andĪ gift. ![]() Problems and good, thought-provoking questions about them. The first thing to understand is that hackers actually like hard Generally be the most effective way to get useful answers out of them, Still, treatingĮxperienced users like hackers in the ways we recommend here will Tolerant of the kind of failures newbies often have. This is a Good Thing users tend to be just a little bit more Often get as good answers from other, more experienced users as from ![]() Now that use of open source has become widespread, you can This guide will teach you how to ask questions in a way more likely You ask the questions as on the difficulty of developing the answer. What you're dealing with, leave us alone and everybody will beĪnswers you get to your technical questions depends as much on the way Unless you know forĬertain that one of the authors is an expert on We are here to show you how to get help from people whoĪctually know about the software or hardware you're dealing with, butĩ9.9% of the time that will not be us. Of this document, you are one of the idiots weĪre talking about. Walk away with the impression you can get it directly from the authors If you're reading this document because you need help, and you Repeatedly be pestered by idiots who think having published thisĭocument makes it our job to solve all the world's technical We have learned the hard way that without such a notice, we will You are a webmaster creating such a link for your project page, pleaseĭisplay prominently near the link notice that we are not a That's fine, it's the use we intended - but if Many project websites link to this document in their sections on Dealing with rudeness On Not Reacting Like A Loser Questions Not To Ask Good and Bad Questions If You Can't Get An Answer How To Answer Questions in a Helpful Way Related Resources Acknowledgements Table of Contents Translations Disclaimer Introduction Before You Ask When You Ask Choose your forum carefully Stack Overflow Web and IRC forums As a second step, use project mailing lists Use meaningful, specific subject headers Make it easy to reply Write in clear, grammatical, correctly-spelled language Send questions in accessible, standard formats Be precise and informative about your problem Volume is not precision Don't rush to claim that you have found a bug Grovelling is not a substitute for doing your homework Describe the problem's symptoms, not your guesses Describe your problem's symptoms in chronological order Describe the goal, not the step Don't ask people to reply by private e-mail Be explicit about your question When asking about code Don't post homework questions Prune pointless queries Don't flag your question as “ Urgent”, even if it is for you Courtesy never hurts, and sometimes helps Follow up with a brief note on the solution How To Interpret Answers RTFM and STFW: How To Tell You've Seriously Screwed Up If you don't understand. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |