The DOI matches its Crossref record; 36 of the 36 references it cites were found in a registry or an index.
Evaluating cues for resuming interrupted programming tasks
Abstract
Developers, like all modern knowledge workers, are frequently interrupted and blocked in their tasks. In this paper we present a contextual inquiry into developers' current strategies for resuming interrupted tasks and investigate the effect of automated cues on improving task resumption. We surveyed 371 programmers on the nature of their tasks, interruptions, task suspension and resumption strategies and found that they rely heavily on note-taking across several types of media. We then ran a controlled lab study to compare the effects of two different automated cues to note taking when resuming interrupted programming tasks. The two cues differed in (1) whether activities were summarized in aggregate or presented chronologically and (2) whether activities were presented as program symbols or as code snippets. Both cues performed well: developers using either cue completed their tasks with twice the success rate as those using note-taking alone. Despite the similar performance of the cues, developers strongly preferred the cue that presents activities chronologically as code snippets.
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
Citations
Cites
Proceedings of the Human Factors and Ergonomics Society 54th Annual Meeting
Kluge, A., Badura, B., Urbas, L., & Burkolter, D. (2010) · Cited by 1,125
Proceedings of the 26th annual conference of the cognitive science society
Dieussaert, K., Ford, M., & Horsten, L. (2004) · Cited by 853
A diary study of task switching and interruptions
Czerwinski, M., Horvitz, E., & Wilhite, S. (2004) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/985692.985715 · Cited by 830
No task left behind?: examining the nature of fragmented work
Mark, G., Gonzalez, V. M., & Harris, J. (2005) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/1054972.1055017 · Cited by 503
Information Needs in Collocated Software Development Teams
Ko, A. J., DeLine, R., & Venolia, G. (2007) · 29th International Conference on Software Engineering (ICSE'07) · doi:10.1109/icse.2007.45 · Cited by 499
Self-citationWhat makes interruptions disruptive? A study of length, similarity, and complexity
Gillie, T., & Broadbent, D. (1989) · Psychological Research · doi:10.1007/bf00309260 · Cited by 490
Trafton, J. G., Altmann, E. M., Brock, D. P., & Mintz, F. E. (2003) · International Journal of Human-Computer Studies · doi:10.1016/s1071-5819(03)00023-5 · Cited by 457
Using task context to improve programmer productivity
Kersten, M., & Murphy, G. C. (2006) · Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering · doi:10.1145/1181775.1181777 · Cited by 452
McFarlane, D. C. (2002) · Human–Computer Interaction · doi:10.1207/s15327051hci1701_2 · Cited by 378
(2001) · Cited by 341
Research works printed but not linked: 1
- Patrick G. S., 2003, Proceedings of OZCHI 2003, 34
Cited by
Are automated debugging techniques actually helping programmers?
Parnin, C., & Orso, A. (2011) · International Symposium on Software Testing and Analysis · doi:10.1145/2001420.2001445 · Cited by 593
“From our previous experience in running programming experiments [20], popular games are ideal subjects, as participants are typically familiar with the behavior of the games and can readily identify game concepts in the source code.”
BackgroundSelf-citationThe Work Life of Developers: Activities, Switches and Perceived Productivity
Meyer, A. N., Barton, L. E., Murphy, G. C., Zimmermann, T., & Fritz, T. (2017) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2017.2656886 · Cited by 170
Bao, L., Li, T., Xia, X., Zhu, K., Li, H., & Yang, X. (2022) · Science China Information Sciences · doi:10.1007/s11432-020-3278-4 · Cited by 188
Resumption strategies for interrupted programming tasks
Parnin, C., & Rugaber, S. (2011) · Software Quality Journal · doi:10.1007/s11219-010-9104-9 · Cited by 103
“experience increased time to perform the task, increased errors, increased loss of knowledge, and increased forgetting to perform critical tasks (Parnin and DeLine 2010).”
BackgroundSelf-citationWhat Predicts Software Developers’ Productivity?
Murphy-Hill, E., Jaspan, C., Sadowski, C., Shepherd, D., Phillips, M., Winter, C., Knight, A., Smith, E., & Jorde, M. (2021) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2019.2900308 · Cited by 100
“Parnin and Rugaber found that resuming tasks after interruption is a frequent and persistent problem for developers [32], caused in part by the need for better tools to assist with task resumption [33].”
Background
Metadata
- Authors
- Parnin, C., & DeLine, R.
- Affiliations
- Georgia Institute of Technology (US)
- Microsoft (United States) (US)
- Venue
- Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
- Publisher
- ACM
- Published
- 2010-04-10
- Pages
- 93-102
- OpenAlex
- W2109228456
- Semantic Scholar
- 7edca52017781cbc90ea6c1100e2eaf642e13359
- Cited by
- 60
- References
- 35
- Citations by year
- 2026: 5 · 2025: 5 · 2024: 4 · 2023: 2 · 2022: 6 · 2021: 3 · 2020: 4 · 2019: 6 · 2018: 1 · 2017: 4 · 2016: 4 · 2015: 3 · 2013: 2 · 2012: 3
- FWCI
- 7.46
- Type
- conference paper
- Language
- en
- Open access
- closed
- Locations
- CHI Conference on Human Factors in Computing Systems (publishedVersion)
- Topics
- Social Sciences › Decision Sciences › Information Systems and Management › Personal Information Management and User Behavior
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Keywords
- task resumption, task suspension, note-taking, developer productivity, code snippets, developer preferences
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
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Evaluating cues for resuming interrupted programming tasks. https://app.cochat.ai/papers/10.1145/1753326.1753342
- The paper
- Parnin, C., & DeLine, R. (2010). Evaluating cues for resuming interrupted programming tasks. Proceedings of the SIGCHI Conference on Human Factors in Computing Systems. https://doi.org/10.1145/1753326.1753342
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.