How to Ask for Technical Help? Evidence-based Guidelines for Writing Questions on Stack Overflow

Abstract

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.

Preprint, to appear in Information and Software Technology

References in corpus (3)

• The Role of Emotions in Contributors Activity: A Case Study on the GENTOO Community
• Recommending Insightful Comments for Source Code using Crowdsourced Knowledge
• Bootstrapping a Lexicon for Emotional Arousal in Software Engineering

Cited by in corpus (15)

• Can We Use SE-specific Sentiment Analysis Tools in a Cross-Platform Setting?
• An empirical assessment of best-answer prediction models in technical Q&A sites
• An empirical study of question discussions on Stack Overflow
• Assessment of Off-the-Shelf SE-specific Sentiment Analysis Tools: An Extended Replication Study
• On Developers' Personality in Large-scale Distributed Projects: The Case of the Apache Ecosystem
• GitHub Discussions: An Exploratory Study of Early Adoption
• How are Project-Specific Forums Utilized? A Study of Participation, Content, and Sentiment in the Eclipse Ecosystem
• Stack Overflow Is Not Dead Yet: Crowd Answers Still Matter
• An Empirical Study on the Characteristics of Question-Answering Process on Developer Forums
• A First Look at Developers' Live Chat on Gitter
• Mining API Usage Scenarios from Stack Overflow
• A Lot of Talk and a Badge: An Exploratory Analysis of Personal Achievements in GitHub
• Reputation Gaming in Stack Overflow
• From Asking to Answering: Getting More Involved on Stack Overflow
• Exploiting the Unique Expression for Improved Sentiment Analysis in Software Engineering Text