An Empirical Study of Obsolete Answers on Stack Overflow

Abstract

Stack Overflow accumulates an enormous amount of software engineering knowledge. However, as time passes, certain knowledge in answers may become obsolete. Such obsolete answers, if not identified or documented clearly, may mislead answer seekers and cause unexpected problems (e.g., using an out-dated security protocol). In this paper, we investigate how the knowledge in answers becomes obsolete and identify the characteristics of such obsolete answers. We find that: 1) More than half of the obsolete answers (58.4%) were probably already obsolete when they were first posted. 2) When an obsolete answer is observed, only a small proportion (20.5%) of such answers are ever updated. 3) Answers to questions in certain tags (e.g., node.js, ajax, android, and objective-c) are more likely to become obsolete. Our findings suggest that Stack Overflow should develop mechanisms to encourage the whole community to maintain answers (to avoid obsolete answers) and answer seekers are encouraged to carefully go through all information (e.g., comments) in answer threads.

14 pages

Cited by in corpus (5)

• Are Human Rules Necessary? Generating Reusable APIs with CoT Reasoning and In-Context Learning
• A Study of Update Request Comments in Stack Overflow Answer Posts
• Automatic API Usage Scenario Documentation from Technical Q&A Sites
• Does the hiding mechanism for Stack Overflow comments work well? No!
• On the Feasibility of Predicting Questions being Forgotten in Stack Overflow