Name
Abstract | ||
|---|---|---|
Interrupted and blocked tasks are a daily reality for professional programmers. Unfortunately, the strategies programmers use to recover lost knowledge and rebuild context when resuming work have not yet been well studied. In this paper, we describe an exploratory analysis performed on 10,000 recorded sessions of 86 programmers and a survey of 414 programmers to understand the various strategies and coping mechanisms developers use to manage interrupted programming tasks. Based on the analysis, we propose a framework for understanding these strategies and suggest how task resumption might be better supported in future development tools. The results suggest that task resumption is a frequent and persistent problem for developers. For example, we find that only 10% of the sessions have programming activity resume in less than 1 min after an interruption, only 7% of the programming sessions involve no navigation to other locations prior to editing. We also found that programmers use multiple coping mechanisms to recover task context when resuming work. |
Year | DOI | Venue |
|---|---|---|
2011 | 10.1007/s11219-010-9104-9 | ICPC |
Keywords | Field | DocType |
Interruption,Resumption strategies,Task context,Task knowledge | Software engineering,Computer science,Coding (social sciences),Human–computer interaction,Software,Programming profession,Encoding (memory) | Journal |
Volume | Issue | ISSN |
19 | 1 | 0963-9314 |
Citations | PageRank | References |
21 | 0.95 | 39 |
Authors | ||
2 | ||
Name | Order | Citations | PageRank |
|---|---|---|---|
| Chris Parnin | 1 | 946 | 47.48 |
| Spencer Rugaber | 2 | 619 | 73.52 |