Cited by 24Software Engineering ResearchPersonal Information Management and User BehaviorSoftware Engineering Techniques and Practices

Resumption strategies for interrupted programming tasks

Parnin, Chris, Rugaber, Spencer·2009·2009 IEEE 17th International Conference on Program Comprehension

Abstract

Interruptions are a daily reality for professional programmers. Unfortunately, the strategies programmers use to recover lost knowledge and resume work have not yet been well studied. In this paper, we perform exploratory analysis on 10,000 recorded programming sessions of 85 programmers to understand the variety of strategies used by programmers for resuming programming tasks. In our study, we find that only 10% of the programming sessions have coding activity start in less than a minute, only 7% of the programming sessions involve no navigation to other locations prior to editing, and find evidence of programmers seeking other sources of task context during task resumption. Based on the analysis, we suggest how task resumption might be better supported in future development tools.

Integrity signals

Registry

Crossref · 10.1109/icpc.2009.5090030

Cites

72 of 72 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • According to Parnin and Rugaber, a major challenge of task resumption is to rebuild the interrupted task's context.

    “According to Parnin and Rugaber, a major challenge of task resumption is to rebuild the interrupted task's context [73].”

    From Detecting Developers' Task Switches and Types (2022) · cites this paper as [73]

Cites

Flagged first, then by citations

Cited by

Sorted by citations

Authors
Parnin, C., & Rugaber, S.
Affiliations
Georgia Institute of Technology (US)
Venue
2009 IEEE 17th International Conference on Program Comprehension
Publisher
IEEE
Published
2009-05
Pages
80-89
OpenAlex
W2142791893
Cited by
24
References
71
Citations by year
2024: 3 · 2022: 2 · 2021: 1 · 2020: 3 · 2019: 1 · 2018: 2 · 2016: 1 · 2014: 2 · 2013: 2 · 2012: 3
FWCI
1.74
Type
conference paper
Language
en
Open access
closed
Locations
IEEE International Conference on Program Comprehension (ICPC) (publishedVersion)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Social Sciences › Decision Sciences › Information Systems and Management › Personal Information Management and User Behavior
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
Keywords
task resumption, interruptions, programmer behavior, source code navigation

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review