Programmer information needs after memory failure
The DOI matches its Crossref record; 9 of the 9 references it cites were found in a registry or an index.
Abstract
Despite its vast capacity and associative powers, the human brain does not deal well with interruptions. Particularly in situations where information density is high, such as during a programming task, recovering from an interruption requires extensive time and effort. Although modern program development environments have begun to recognize this problem, none of these tools take into account the brain's structure and limitations. In this paper, we present a conceptual framework for understanding the strengths and weaknesses of human memory, particularly with respect to it ability to deal with work interruptions. The framework explains empirical results obtained from experiments in which programmers were interrupted while working. Based on the framework, we discuss programmer information needs that development tools must satisfy and suggest several memory aids such tools could provide. We also describe our prototype implementation of these memory aids.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
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
Ko, A. J., Myers, B. A., Coblenz, M. J., & Aung, H. H. (2006) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2006.116 · Cited by 685 · cited 1×
“[24] observed that programmers used cues, such as opendocument tabs and scrollbars, for maintaining context during their programming tasks.”
How We Refactor, and How We Know It
Murphy-Hill, E., Parnin, C., & Black, A. P. (2012) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2011.41 · Cited by 547
Self-citationInformation 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 · cited 1×
“For example, developers can become blocked when coordinating with other developers (waiting for a busy teammate to become available again or finish a task) [19].”
BackgroundUsing 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
SenseCam: A wearable camera that stimulates and rehabilitates autobiographical memory
Hodges, S., Berry, E., & Wood, K. (2011) · Memory · doi:10.1080/09658211.2011.605591 · Cited by 181 · cited 2×
“have shown that when a sequential presentation of events (pictures) from a past experience is given, that presentation can be more effective at stimulating recall than when other contextual details (names or locations) are given [29], [17].”
BackgroundReynolds, J. R., West, R., & Braver, T. (2009) · Cerebral Cortex · doi:10.1093/cercor/bhn164 · Cited by 181 · cited 1×
“anterior prefrontal cortex (lateral Brodmann area 10) of the brain and is supported by memory processes distinct from those supporting other types of memory [8].”
BackgroundResumption strategies for interrupted programming tasks
Parnin, C., & Rugaber, S. (2011) · Software Quality Journal · doi:10.1007/s11219-010-9104-9 · Cited by 103
Self-citationEvaluating Cues for Resuming Interrupted Programming Tasks
Parnin, C., & DeLine, R. (2010) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/1753326.1753342 · Cited by 60 · cited 3×
“Note-taking is a also common strategy to retain information about a programmed task when interrupted; however, such notes can often be incomplete and lead to resumption failures [26].”
BackgroundSelf-citation
Cited by
Understanding understanding source code with functional magnetic resonance imaging
Siegmund, J., Kästner, C., Apel, S., Parnin, C., Bethmann, A., Leich, T., Saake, G., & Brechmann, A. (2014) · Proceedings of the 36th International Conference on Software Engineering · doi:10.1145/2568225.2568252 · Cited by 219
“Parnin compiled a literature review of cognitive neuroscience and proposed a model for understanding different memory types and brain areas exercised by different types of programming tasks [52].”
BackgroundSelf-citationWhat help do developers seek, when and how?
Li, H., Xing, Z., Peng, X., & Zhao, W. (2013) · 2013 20th Working Conference on Reverse Engineering (WCRE) · doi:10.1109/wcre.2013.6671289 · Cited by 81
The sky is not the limit: multitasking across GitHub projects
Vasilescu, B., Blincoe, K., Xuan, Q., Casalnuovo, C., Damian, D., Devanbu, P., & Filkov, V. (2016) · Proceedings of the 38th International Conference on Software Engineering · doi:10.1145/2884781.2884875 · Cited by 77
“When developers resume a task after an interruption, they must reconstruct the task’s context [38, 40–42].”
MethodWork fragmentation in developer interaction data
Cruz, L. C., Sanchez, H., González, V. M., & Robbes, R. (2017) · Journal of Software: Evolution and Process · doi:10.1002/smr.1839 · Cited by 6
Metadata
- Authors
- Parnin, C., & Rugaber, S.
- Venue
- 2012 20th IEEE International Conference on Program Comprehension (ICPC)
- Publisher
- IEEE
- Published
- 2012-06
- Pages
- 123-132
- OpenAlex
- W2150429773
- Cited by
- 36
- References
- 9
- FWCI
- 9.08
- Type
- conference paper
- Language
- en
- Open access
- closed
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: Programmer information needs after memory failure. https://app.cochat.ai/papers/10.1109/icpc.2012.6240479
- The paper
- Parnin, C., & Rugaber, S. (2012). Programmer information needs after memory failure. 2012 20th IEEE International Conference on Program Comprehension (ICPC). https://doi.org/10.1109/icpc.2012.6240479
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.