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

Nader Dehghani

dblp:332/5618 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
1since 2021 · last 2022
—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
Empirical software engineering · 100%
Human-computer interaction and pervasive computing
1 paper
Collaborative and social computing · 100%

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

TopicWeightPapersLastEvidence papers
Empirical software engineering › developer studies › developer behavior
developer productivity
0.612022
Workgraph: personal focus vs. interruption for engineers at Meta · ESEC/SIGSOFT FSE 2022
Collaborative and social computing
computer-supported cooperative work
0.212022
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.1
YearPublicationVenuePosition
2022 Workgraph: personal focus vs. interruption for engineers at Meta
abstract
All 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 FSE5