“There was a time in my life, and that time is still persistent even now, when every question that I asked on SO was flagged, and I was banned for 7 days with a message which said something like this - "It seems your basic concepts are unclear. Kindly revise then and get back to us" I swear to God I was so pissed off. Here I am, genuinely asking for help…”
How to Ask for Technical Help? Evidence-based Guidelines for Writing Questions on Stack Overflow
Context: The success of Stack Overflow and other community-based question-and-answer (Q&A) sites depends mainly on the will of their members to answer others' questions. In fact, when formulating requests on Q&A sites, we are not simply seeking for information. Instead, we are also asking for other people's help and feedback. Understanding the dynamics of the participation in Q&A communities is essential to improve the value of crowdsourced knowledge. Objective: In this paper, we investigate how information seekers can increase the chance of eliciting a successful answer to their questions on Stack Overflow by focusing on the following actionable factors: affect, presentation quality, and time. Method: We develop a conceptual framework of factors potentially influencing the success of questions in Stack Overflow. We quantitatively analyze a set of over 87K questions from the official Stack Overflow dump to assess the impact of actionable factors on the success of technical requests. The information seeker reputation is included as a control factor. Furthermore, to understand the role played by affective states in the success of questions, we qualitatively analyze questions containing positive and negative emotions. Finally, a survey is conducted to understand how Stack Overflow users perceive the guideline suggestions for writing questions. Results: We found that regardless of user reputation, successful questions are short, contain code snippets, and do not abuse with uppercase characters. As regards affect, successful questions adopt a neutral emotional style. Conclusion: We provide evidence-based guidelines for writing effective questions on Stack Overflow that software engineers can follow to increase the chance of getting technical help. As for the role of affect, we empirically confirmed community guidelines that suggest avoiding rudeness in question writing.
候选层:至少 2 个不同的人、在 2 个不同月份提到过,还没到主书架的 3 人 3 个月。没有做立场标注,所以只写“被提及”。
HN 书评
没有评论直接链到它;下面是它被提交的讨论串里回复最多的评论(不计入统计)“To be brutally honest this is absolutely pointless. It is basically confirming simple online etiquette produces best results.”
“a mod can close find support in the SO guidelines to close any question they wish. a tightly defined, clearly written question with a single correct anwswer? Rejected: RTFM a question with more than one correct answer (but which almost certainly has a "best answer" which a community like SO is in the obvious best position to judge)? Rejected: subjecti…”
- Evidence-Based Guidelines for Writing Questions on Stack Overflow ↗lainon · 2017-12-26 · 75 分
- How to Ask for Technical Help? (2017) ↗billme · 2020-05-14 · 2 分