Demo Data from SIGIR 2026 / reviewers in the wild / expert
Alexander Suh
dblp:261/9639
· DBLP profile ↗
1ranked-venue papers
1as first author
0since 2021 · last 2020
0000-0002-6079-1145ORCID · reported
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1 · 1 first-author
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Software engineering, system software, and programming languages
1 paper |
Empirical software engineering · 87% Software maintenance and evolution · 13% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Empirical software engineering
mining software repositories |
0.4 | 1 | 2020 | Adapting bug prediction models to predict reverted commits at Wayfair · ESEC/SIGSOFT FSE 2020 |
Empirical software engineering
software defect prediction |
0.4 | 1 | 2020 | Adapting bug prediction models to predict reverted commits at Wayfair · ESEC/SIGSOFT FSE 2020 |
Software maintenance and evolution › release engineering
continuous integration |
0.1 | 1 | 2020 | Adapting bug prediction models to predict reverted commits at Wayfair · ESEC/SIGSOFT FSE 2020 |
Methods — techniques the papers use, named apart from their topics
machine learning · 0.4
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2020 | Adapting bug prediction models to predict reverted commits at WayfairabstractResearchers have proposed many algorithms to predict software bugs. Given a software entity (e.g., a file or method), these algorithms predict whether the entity is bug-prone. However, since these algorithms cannot identify specific bugs, this does not tend to be particularly useful in practice. In this work, we adapt this prior work to the related problem of predicting whether a commit is likely to be reverted. Given the batch nature of continuous integration deployment at scale, this allows developers to find time-sensitive bugs in production more quickly. The models in this paper are based on features extracted from the revision history of a codebase that are typically used in bug prediction. Our experiments, performed on the three main repositories for the Wayfair website, show that our models can rank reverted commits above 80% of non-reverted commits on average. Moreover, when given to Wayfair developers, our models reduce the amount of time needed to find certain kinds of bugs by 55%. Wayfair continues to use our findings and models today to help find bugs during software deployments. Alexander Suh |
ESEC/SIGSOFT FSE | 1 |