EDBT 2026 Demo / reviewers in the wild / expert
Mike Buller
dblp:419/6071
· DBLP profile ↗
1ranked-venue papers
0as first author
1since 2021 · last 2025
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1 · 1 since 2021
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 |
Software maintenance and evolution · 100% |
Topics — the 2 heaviest of 2, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Software maintenance and evolution › code review
automated code review |
0.9 | 1 | 2025 | What Types of Code Review Comments Do Developers Most Frequently Resolve? · ASE 2025 |
Software maintenance and evolution
code review |
0.9 | 1 | 2025 | What Types of Code Review Comments Do Developers Most Frequently Resolve? · ASE 2025 |
Methods — techniques the papers use, named apart from their topics
large language model · 0.9LLM-as-a-judge · 0.9
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2025 | What Types of Code Review Comments Do Developers Most Frequently Resolve?abstractLarge language model (LLM)-powered code review automation tools have been introduced to generate code review comments. However, not all generated comments will drive code changes. Understanding what types of generated review comments are likely to trigger code changes is crucial for identifying those that are actionable. In this paper, we set out to investigate (1) the types of review comments written by humans and LLMs, and (2) the types of generated comments that are most frequently resolved by developers. To do so, we developed an LLM-as-a-Judge to automatically classify review comments based on our own taxonomy of five categories. Our empirical study confirms that (1) the LLM reviewer and human reviewers exhibit distinct strengths and weaknesses depending on the project context, and (2) readability, bugs, and maintainability-related comments had higher resolution rates than those focused on code design. These results suggest that a substantial proportion of LLM-generated comments are actionable and can be resolved by developers. Our work highlights the complementarity between LLM and human reviewers and offers suggestions to improve the practical effectiveness of LLM-powered code review tools. Saul Goldman, Hong Yi Lin, Jirat Pasuksmit, Patanamon Thongtanunam, Chakkrit Tantithamthavorn, Ray Zhang 0004, Ali Behnaz, Michael Siers, Ryan Jiang, Mike Buller, Minwoo Jeong |
ASE | 12 |