Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Ben Holtz

dblp:277/9036 · DBLP profile ↗
← Back
2ranked-venue papers
0as first author
2since 2021 · last 2023
0000-0002-8020-0357ORCID · corroborated

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1 · 1 since 2021Human-computer interaction and ubiquitous computing · 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
2 papers
Empirical software engineering · 71% Software maintenance and evolution · 29%
Human-computer interaction and pervasive computing
1 paper
Collaborative and social computing · 100%

Topics — the 4 heaviest of 5, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Empirical software engineering › developer studies › developer behavior
developer productivity
0.712023
Using Logs Data to Identify When Software Engineers Experience Flow or Focused Work · CHI 2023
Software maintenance and evolution
code review
0.612022
Engineering Impacts of Anonymous Author Code Review: A Field Experiment · IEEE Trans. Software Eng. 2022
Empirical software engineering
developer studies
0.612022
Engineering Impacts of Anonymous Author Code Review: A Field Experiment · IEEE Trans. Software Eng. 2022
Empirical software engineering
mining software repositories
0.212023
Using Logs Data to Identify When Software Engineers Experience Flow or Focused Work · CHI 2023

Methods — techniques the papers use, named apart from their topics

field experiment · 1.1survey data · 0.7mixed-methods · 0.7machine learning · 0.7diary data · 0.7
YearPublicationVenuePosition
2023 Using Logs Data to Identify When Software Engineers Experience Flow or Focused Work
abstract
Beyond self-report data, we lack reliable and non-intrusive methods for identifying flow. However, taking a step back and acknowledging that flow occurs during periods of focus gives us the opportunity to make progress towards measuring flow by isolating focused work. Here, we take a mixed-methods approach to design a logs-based metric that leverages machine learning and a comprehensive collection of logs data to identify periods of related actions (indicating focus), and validate this metric against self-reported time in focus or flow using diary data and quarterly survey data. Our results indicate that we can determine when software engineers at a large technology company experience focused work which includes instances of flow. This metric speaks to engineering work, but can be leveraged in other domains to non-disruptively measure when people experience focus. Future research can build upon this work to identify signals associated with other facets of flow.
Adam Brown, Sarah D'Angelo, Ben Holtz, Ciera Jaspan, Collin Green
CHI3
2022 Engineering Impacts of Anonymous Author Code Review: A Field Experiment
abstract
Code review is a powerful technique to ensure high quality software and spread knowledge of best coding practices between engineers. Unfortunately, code reviewers may have biases about authors of the code they are reviewing, which can lead to inequitable experiences and outcomes. In principle, anonymous author code review can reduce the impact of such biases by withholding an author's identity from a reviewer. In this paper, to understand the engineering effects of using author anonymous code review in a practical setting, we applied the technique to 5217 code reviews performed by 300 software engineers at Google. Our results suggest that during anonymous author code review, reviewers can frequently guess authors’ identities; that focus is reduced on reviewer-author power dynamics; and that the practice poses a barrier to offline, high-bandwidth conversations. Based on our findings, we recommend that those who choose to implement anonymous author code review should reveal the time zone of the author by default, have a break-the-glass option for revealing author identity, and reveal author identity directly after the review.
Emerson R. Murphy-Hill, Jillian Dicker, Margaret Morrow Hodges, Carolyn D. Egelman, Ciera Jaspan, Elizabeth Kammer 0001, Ben Holtz, Matthew Jorde, Andrea Knight, Collin Green
IEEE Trans. Software Eng.8