What would other programmers do: suggesting solutions to error messages

By Bjoern Hartmann, Daniel MacDougall, Joel Brandt, Scott R. Klemmer. 2010

310 citations recorded by the source corpus.

Subfields: Information Systems, Software, Code Generation & Program Synthesis, Program Analysis & Verification

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Information Systems

In Software

In Code Generation & Program Synthesis

In Program Analysis & Verification

Citations in the corpus

SPoC: Search-based Pseudocode to Code (2019, background): “Other work identiﬁes error locations by interpreting compiler error messages [13, 5].”
Soylent: a word processor with a crowd inside (2010, background): “Soylent is influenced by prior work on crowdsourced interfaces (e.g., [1, 9, 24]).”
Design lessons from the fastest q&a site in the west (2011, unknown): “For questions about programming, researchers have also integrated techniques for finding help, examples, and debugging strategies directly into programming environments [5,12].”
Compilation Error Repair: For the Student Programs, From the Student Programs (2018, methodology): “The techniques adopted by TRACER for program repair are motivated by a common observation [6, 7] that in practice, programmers (especially novice programmers) use a rather small subset of rules and productions of the entire grammar.”
Emergent, crowd-scale programming practice in the IDE (2014, background): “Pattern finding tools usually need to abstract away some properties if they are to find meaningful statistical patterns [18, 3, 9].”
Example-centric programming: integrating web search into the development environment (2010, background): “For example, to decipher a cryptic error message, one may want to use program output as the search query [16].”
CODIT: Code Editing With Tree-Based Neural Models (2018, background): “Finally, there are domainspecific approaches, such as error handling code generation [95], [96], API-related changes [9], [10], [11], [12], [13], [14], [97], automatic refactorings [15], [16], [17], [18], etc.”
A survey of the use of crowdsourcing in software engineering (2017, methodology): “The results indicated that the tool was able to help the students fix compile-time errors faster, and when compared with HelpMeOut, BlueFix’s suggestions were 19.52% higher in precision.”