I Know What You Did Last Summer - An Investigation of How Developers Spend Their Time
The DOI matches its Crossref record; 6 of the 6 references it cites were found in a registry or an index.
Abstract
Developing software is a complex mental activity, requiring extensive technical knowledge and abstraction capabilities. The tangible part of development is the use of tools to read, inspect, edit, and manipulate source code, usually through an IDE (integrated development environment). Common claims about software development include that program comprehension takes up half of the time of a developer, or that certain UI (user interface) paradigms of IDEs offer insufficient support to developers. Such claims are often based on anecdotal evidence, throwing up the question of whether they can be corroborated on more solid grounds. We present an in-depth analysis of how developers spend their time, based on a fine-grained IDE interaction dataset consisting of ca. 740 development sessions by 18 developers, amounting to 200 hours of development time and 5 million of IDE events. We propose an inference model of development activities to precisely measure the time spent in editing, navigating and searching for artifacts, interacting with the UI of the IDE, and performing corollary activities, such as inspection and debugging. We report several interesting findings which in part confirm and reinforce some common claims, but also disconfirm other beliefs about software development.
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
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 2×
“claimed that understanding is also achieved by navigating source code fragments [15], and that such process occupies around 35% of the total development time.”
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 · cited 1×
“Researchers also studied the impact of work fragmentation [34], [35], [23].”
How are Java software developers using the Eclipse IDE?
Murphy, G. C., Kersten, M., & Findlater, L. (2006) · IEEE Software · doi:10.1109/ms.2006.105 · Cited by 413 · cited 3×
“used the data collected by MYLAR to study how Java developers use the Eclipse IDE [14], finding that developers use most of the Eclipse perspectives while developing, and that keyboard shortcuts are a frequently used alternative to faster reach some IDE features.”
Using psycho-physiological measures to assess task difficulty in software development
Fritz, T., Begel, A., Müller, S. C., Yigit-Elliott, S., & Züger, M. (2014) · Proceedings of the 36th International Conference on Software Engineering · doi:10.1145/2568225.2568266 · Cited by 262 · cited 1×
“used data from psycho-physiological sensors to assess the nominal difficulty of code comprehension tasks [30].”
Automated Identification of Tasks in Development Sessions
Coman, I. D., & Sillitti, A. (2008) · 2008 16th IEEE International Conference on Program Comprehension · doi:10.1109/icpc.2008.16 · Cited by 38 · cited 1×
“Coman and Sillitti collected low-level events and presented a technique to split sessions into task-related sub-sessions [33].”
An Industrial Case Study of Program Artifacts Viewed During Maintenance Tasks
Zou, L., & Godfrey, M. W. (2006) · 2006 13th Working Conference on Reverse Engineering · doi:10.1109/wcre.2006.12 · Cited by 20
Cited by
Becker, B. A., Denny, P., Finnie-Ansley, J., Luxton-Reilly, A., Prather, J., & Santos, E. A. (2023) · Proceedings of the 54th ACM Technical Symposium on Computer Science Education V. 1 · doi:10.1145/3545945.3569759 · Cited by 401
Measuring Program Comprehension: A Large-Scale Field Study with Professionals
Xia, X., Bao, L., Lo, D., Xing, Z., Hassan, A. E., & Li, S. (2018) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2017.2734091 · Cited by 326
Klaib, A. F., Alsrehin, N. O., Melhem, W. Y., Bashtawi, H. O., & Magableh, A. A. (2021) · Expert Systems with Applications · doi:10.1016/j.eswa.2020.114037 · Cited by 263
The 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
Today was a good day: The daily life of software developers
Meyer, A. N., Barr, E. T., Bird, C., & Zimmermann, T. (2021) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2019.2904957 · Cited by 123
Metadata
- Authors
- Minelli, R., Mocci, A., & Lanza, M.
- Venue
- 2015 IEEE 23rd International Conference on Program Comprehension
- Publisher
- IEEE
- Published
- 2015-05
- Pages
- 25-35
- OpenAlex
- W4247854836
- Cited by
- 181
- References
- 6
- FWCI
- 8.19
- 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
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.