What is this?
A Traditional Chinese (繁體中文) translation of Eric S. Raymond and Rick Moen's classic essay 'How To Ask Questions The Smart Way', which teaches programmers how to phrase technical questions so experienced hackers will actually want to answer them.
A Traditional Chinese (繁體中文) translation of Eric S. Raymond and Rick Moen's classic essay 'How To Ask Questions The Smart Way', which teaches programmers how to phrase technical questions so experienced hackers will actually want to answer them.Is this an original essay or a translation of something else?It is a translation, not original work: based on ESR/Rick Moen's English version 3.10, originally translated by Gasolin in 2010 and updated/maintained by Ryan Wu since 2015. A Simplified Chinese edition is also linked from the repo.
It is a translation, not original work: based on ESR/Rick Moen's English version 3.10, originally translated by Gasolin in 2010 and updated/maintained by Ryan Wu since 2015. A Simplified Chinese edition is also linked from the repo.What is the guide's actual advice before posting a question?Before asking anywhere, it tells you to search forum archives, search the web, read the manual, read the FAQ, experiment yourself, ask a knowledgeable friend, and (for developers) read the source code - and to mention in your post which of these you already tried.
Before asking anywhere, it tells you to search forum archives, search the web, read the manual, read the FAQ, experiment yourself, ask a knowledgeable friend, and (for developers) read the source code - and to mention in your post which of these you already tried.Will the authors of this guide personally answer my tech support question?No - the README explicitly warns that the guide itself provides no support for any project; readers who email the maintainers expecting help are ignored.
No - the README explicitly warns that the guide itself provides no support for any project; readers who email the maintainers expecting help are ignored.Who should read this?Anyone posting technical questions in forums, mailing lists, Stack Exchange sites or IRC who wants useful answers from open-source developers and hackers, plus experienced users who want a reference to point newbies to.
Anyone posting technical questions in forums, mailing lists, Stack Exchange sites or IRC who wants useful answers from open-source developers and hackers, plus experienced users who want a reference to point newbies to.What are the main topics covered in the table of contents?Sections include choosing the right forum, using Stack Overflow/Stack Exchange correctly, project mailing list etiquette, how to write a clear subject line and well-formatted question, how to interpret answers, handling rude responses, and a list of questions not to ask.
Sections include choosing the right forum, using Stack Overflow/Stack Exchange correctly, project mailing list etiquette, how to write a clear subject line and well-formatted question, how to interpret answers, handling rude responses, and a list of questions not to ask.Where does the guide say you should actually post your question?It recommends searching Google first, then trying Stack Exchange sites (Stack Overflow for code, Super User for general computer questions, Server Fault for sysadmin topics), local user-group forums or IRC channels, and finally a project's public mailing list rather than emailing an individual developer.
It recommends searching Google first, then trying Stack Exchange sites (Stack Overflow for code, Super User for general computer questions, Server Fault for sysadmin topics), local user-group forums or IRC channels, and finally a project's public mailing list rather than emailing an individual developer.Is there a Simplified Chinese version of this guide?Yes, the README links to a separate Simplified Chinese (简体中文) translation alongside this Traditional Chinese one.
Yes, the README links to a separate Simplified Chinese (简体中文) translation alongside this Traditional Chinese one.Why does the guide warn against emailing maintainers privately?Because a question useful enough to ask one developer is useful to the whole project, and public mailing lists get archived and indexed by search engines so future askers with the same problem can find the answer without re-asking.
Because a question useful enough to ask one developer is useful to the whole project, and public mailing lists get archived and indexed by search engines so future askers with the same problem can find the answer without re-asking.What are similar projects?architecture-decision-record, python-guide, hacker-laws-zh, tensorflow-zh, vim-galore-zh_cn, unmaintainable-code, zh-google-styleguide, eng-practices
architecture-decision-record, python-guide, hacker-laws-zh, tensorflow-zh, vim-galore-zh_cn, unmaintainable-code, zh-google-styleguide, eng-practicesWhich topics is it in?chinese-traditional, communication, software-engineering, translation, best-practices, reference, guide, learning-resources, documentation, developers, tutorial, education
chinese-traditional, communication, software-engineering, translation, best-practices, reference, guide, learning-resources, documentation, developers, tutorial, education