How to ask a good question

You are welcome to join the SegmentFault community. We provide you with a pure and high-quality technical exchange platform in the form of technical Q&A, technical columns and other products.

First, let's take a quick look at the whole process of asking questions in the community:

The birth of a question will go through the above links: retrieving whether there is an answer - organizing the question - publishing the question - entering the review and other links.

Today we mainly talk about: "How to ask a good question" Here are some tips for reference~

标题：精准定位你的问题哦

When asking questions, priority should be given to whether the respondent can clearly and accurately understand the meaning to be expressed. Community administrators also take this standard as the top priority when reviewing.

A normal title can describe the problem you encounter in one sentence, so that developers across the screen can quickly locate and locate whether they want to open this question (that is, can you answer it). Of course, sometimes the problem may not be clearly described in one sentence, so the title, the general point can be "about the XXX problems encountered in the process of implementing XXX with XXX"

Also, avoid titles like this:

• The problem statement is too brief : often just one sentence or even a title. (Example: The title is "How to implement a Taobao-like website?")
• A long list of titles of "Tang Seng Chanting" : "Look at the great gods...", "Although I know this problem is very basic, but I still can't solve it, please take a look at it", "How is this balabala, is there a great god?" did this project"...

Regarding a good title, the article of the guiding community:

Some explanations of the SegmentFault community questioning criteria
The developer who asked the question, can you organize your question and code before throwing it out? - How to ask questions in a structured way

问题详情：注意上下文，描述详尽

The content of a question is like a good case-solving report. It must have an objective and detailed description, as well as a record of trying solutions.

• Provide a detailed problem context : The running of the program will depend on its own execution environment and the corresponding parameters of various configuration items, and describe the environment in which the problem occurs as completely as possible.
• Whether the problem can be reproduced, how to reproduce : Reproduce the error steps in detail, and find out the general pattern of problem recurrence.
• Describe the solutions used before: Briefly record all the methods used before, which can be logs, try catch information in the program, screenshots of errors, etc.

Detailed content guide article: Programmer, do you really ask questions?

In addition, after the text is organized, you should also pay attention to the typesetting. This site supports Markdown syntax. Click here to get the skills ~

Finally, as Joyqi said: When we have gradually grown into an important force in the domestic technical Q&A field, we have been unable to escape the responsibility on our shoulders, so we hope to lead the entire community to make progress together and jointly create a technology that belongs to us. home.

Looking forward to your learning and progress in the community~

---