Saya menemukan bacaan yang cukup bagus mengenai cara bertanya di forum.. karena kebanyakan member forum ini hanya bisa bertanya dan malas mencari jawaban..
walau bacaan ini berbau IT, namun bisa diambil agar kita LEBIH CERDAS dalam BERTANYA..
When You Ask
Choose your forum carefullyBe sensitive in choosing where you ask your question. You are likely to be ignored, or written off as a loser, if you:
- post your question to a forum where it's off topic
- post a very elementary question to a forum where advanced technical questions are expected, or vice-versa
- cross-post to too many different newsgroups
- post a personal e-mail to somebody who is neither an acquaintance of yours nor personally responsible for solving your problem
Use meaningful, specific subject headersOn mailing lists, newsgroups or Web forums, the subject header is your golden opportunity to attract qualified experts' attention in around 50 characters or fewer. Don't waste it on babble like “Please help me†(let alone “PLEASE HELP ME!!!!â€; messages with subjects like that get discarded by reflex). Don't try to impress us with the depth of your anguish; use the space for a super-concise problem description instead.
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.
Stupid: HELP! Video doesn't work properly on my laptop!
Smart:X.org 6.8.1 misshapen mouse cursor, Fooware MV1005 vid. chipset
Smarter: X.org 6.8.1 mouse cursor on Fooware MV1005 vid. chipset - is misshapen
Write in clear, grammatical, correctly-spelled languageWe'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 to
be precise; 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.Be precise and informative about your problem
- Describe the symptoms of your problem or bug carefully and clearly.
- Describe the environment in which it occurs (machine, OS, application, whatever). Provide your vendor's distribution and release level (e.g.: “Fedora Core 7â€, “Slackware 9.1â€, etc.).
- 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.
- Describe any possibly relevant recent changes in your computer or software configuration.
- If at all possible, provide a way to reproduce the problem in a controlled environment.
Source : http://www.catb.org/~esr/faqs/smart-questions.html
maaf bro kalau bisa terjemahannya, sudah di coba ke google translate malah makin pusing bacanya ^:)^
wah artikel yang menarik lohh, ini kira kira dengan tempat terbatas di title atau judul ketika kita membuat thread /membuat post dengan kata kata yang di pilih dengan baik hingga memberi umpan balik atau menarik pembaca untuk membaca thread tersebut.