Demo Data from VLDB 2026 / reviewers in the wild / expert
Sergii Shmarkatiuk
dblp:145/4021
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2014
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1
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 · 67% Empirical software engineering · 33% | |
| Human-computer interaction and pervasive computing
1 paper |
Collaborative and social computing · 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
code change analysis |
0.2 | 1 | 2014 | How do centralized and distributed version control systems impact software changes? · ICSE 2014 |
Empirical software engineering
mining software repositories |
0.2 | 1 | 2014 | How do centralized and distributed version control systems impact software changes? · ICSE 2014 |
Software maintenance and evolution › software configuration management
version control |
0.2 | 1 | 2014 | How do centralized and distributed version control systems impact software changes? · ICSE 2014 |
Collaborative and social computing › team collaboration
collaborative software development |
0.1 | 1 | 2014 | How do centralized and distributed version control systems impact software changes? · ICSE 2014 |
Methods — techniques the papers use, named apart from their topics
empirical study · 0.4
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2014 | How do centralized and distributed version control systems impact software changes?abstractDistributed Version Control Systems (DVCS) have seen an increase in popularity relative to traditional Centralized Version Control Systems (CVCS). Yet we know little on whether developers are benefitting from the extra power of DVCS. Without such knowledge, researchers, developers, tool builders, and team managers are in the danger of making wrong assumptions. Caius Brindescu, Mihai Codoban, Sergii Shmarkatiuk, Danny Dig |
ICSE | 3 |