EDBT 2026 Demo / reviewers in the wild / expert
Benedikt Schesch
dblp:322/9334
· DBLP profile ↗
3ranked-venue papers
2as first author
3since 2021 · last 2026
0009-0002-2885-3067ORCID · corroborated
Domains — the database's venue-derived domains; a paper can count in several
Artificial intelligence and machine learning · 2 · 1 first-author · 2 since 2021Software engineering, systems software and programming languages · 1 · 1 first-author · 1 since 2021Graphics, computer vision, multimedia, augmented reality and games · 1 · 1 first-author · 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 · 87% Software testing · 13% | |
| Artificial intelligence
1 paper |
Graph learning · 100% |
Topics — the 4 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Software maintenance and evolution › software merging
merge conflict resolution |
0.8 | 1 | 2024 | Evaluation of Version Control Merge Tools · ASE 2024 |
Software maintenance and evolution › software configuration management
version control |
0.8 | 1 | 2024 | Evaluation of Version Control Merge Tools · ASE 2024 |
Machine learning › Graph learning
graph neural network |
0.7 | 1 | 2023 | Agent-based Graph Neural Networks · ICLR 2023 |
Software testing
regression testing |
0.2 | 1 | 2024 | Evaluation of Version Control Merge Tools · ASE 2024 |
Methods — techniques the papers use, named apart from their topics
empirical evaluation · 0.8message passing · 0.7
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2026 | Merge-Bench: Resolve Merge Conflicts with Large Language Models
Benedikt Schesch, Michael D. Ernst |
ICPR (7) | 1 |
| 2024 | Evaluation of Version Control Merge ToolsabstractA version control system, such as Git, requires a way to integrate changes from different developers or branches. Given a merge scenario, a merge tool either outputs a clean integration of the changes, or it outputs a conflict for manual resolution. A clean integration is correct if it preserves intended program behavior, and is incorrect otherwise (e.g., if it causes a test failure). Manual resolution consumes valuable developer time, and correcting a defect introduced by an incorrect merge is even more costly. Benedikt Schesch, Ryan Featherman, Kenneth J. Yang, Ben R. Roberts, Michael D. Ernst |
ASE | 1 |
| 2023 | Agent-based Graph Neural Networks
Karolis Martinkus, Pál András Papp, Benedikt Schesch, Roger Wattenhofer |
ICLR | 3 |