Demo Data from SIGIR 2026 / reviewers in the wild / expert
Yifen Chen
dblp:332/6107
· DBLP profile ↗
2ranked-venue papers
1as first author
2since 2021 · last 2023
0009-0002-0761-5860ORCID · reported
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 2 · 1 first-author · 2 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
2 papers |
Empirical software engineering · 80% Software maintenance and evolution · 20% | |
| Human-computer interaction and pervasive computing
1 paper |
Collaborative and social computing · 100% |
Topics — the 5 heaviest of 5, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Empirical software engineering › developer studies › developer behavior
developer productivity |
1.2 | 2 | 2023 | Modeling the Centrality of Developer Output with Software Supply Chains · ESEC/SIGSOFT FSE 2023 Workgraph: personal focus vs. interruption for engineers at Meta · ESEC/SIGSOFT FSE 2022 |
Empirical software engineering
developer studies |
0.7 | 1 | 2023 | Modeling the Centrality of Developer Output with Software Supply Chains · ESEC/SIGSOFT FSE 2023 |
Empirical software engineering
mining software repositories |
0.7 | 1 | 2023 | Modeling the Centrality of Developer Output with Software Supply Chains · ESEC/SIGSOFT FSE 2023 |
Software maintenance and evolution
software supply chain |
0.7 | 1 | 2023 | Modeling the Centrality of Developer Output with Software Supply Chains · ESEC/SIGSOFT FSE 2023 |
Collaborative and social computing
computer-supported cooperative work |
0.2 | 1 | 2022 | Workgraph: personal focus vs. interruption for engineers at Meta · ESEC/SIGSOFT FSE 2022 |
Methods — techniques the papers use, named apart from their topics
log analysis · 1.1pagerank · 0.7katz centrality · 0.7
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2023 | Modeling the Centrality of Developer Output with Software Supply ChainsabstractRaw developer output, as measured by the number of changes a developer makes to the system, is simplistic and potentially misleading measure of productivity as new developers tend to work on peripheral and experienced developers on more central parts of the system. In this work, we use Software Supply Chain (SSC) networks and Katz centrality and PageRank on these networks to suggest a more nuanced measure of developer productivity. Our SSC is a network that represents the relationships between developers and artifacts that make up a system. We combine author-to-file, co-changing files, call hierarchies, and reporting structure into a single SSC and calculate the centrality of each node. The measures of centrality can be used to better understand variations in the impact of developer output at Meta. We start by partially replicating prior work and show that the raw number of developer commits plateaus over a project-specific period. However, the centrality of developer work grows for the entire period of study, but the growth slows after one year. This implies that while raw output might plateau, more experienced developers work on more central parts of the system. Finally, we investigate the incremental contribution of SSC attributes in modeling developer output. We find that local attributes such as the number of reports and the specific project do not explain much variation (𝑅2 = 5.8%). In contrast, adding Katz centrality or PageRank produces a model with an 𝑅2 above 30%. SSCs and their centrality provide valuable insights into the centrality and importance of a developer’s work. Audris Mockus, Peter C. Rigby, Rui Abreu 0001, Parth Suresh, Yifen Chen, Nachiappan Nagappan |
ESEC/SIGSOFT FSE | 5 |
| 2022 | Workgraph: personal focus vs. interruption for engineers at MetaabstractAll engineers dislike interruptions because it takes away from the deep focus time needed to write complex code. Our goal is to reduce unnecessary interruptions at . We first describe our Workgraph platform that logs how engineers use our internal work tools at . Using these anonymized logs, we create sessions. sessions are defined in opposition to interruption and are the amount of time until the engineer is interrupted by, for example, a work chat message. Yifen Chen, Peter C. Rigby, Nader Dehghani, Qianying Huang, Peter Cottle, Clayton Andrews, Noah Lee, Nachiappan Nagappan |
ESEC/SIGSOFT FSE | 1 |