Maintaining Mental Models: A Study of Developer Work Habits (2006)
Cached
Download Links
- [research.microsoft.com]
- [research.microsoft.com]
- [plg.uwaterloo.ca]
- [research.microsoft.com]
- [research.microsoft.com]
- [www.cs.bgu.ac.il]
- [www.microsoft.com]
- [www.cs.cmu.edu]
- [www.ics.uci.edu]
- [www.st.cs.uni-saarland.de]
- [www.ics.uci.edu]
- [cs.gmu.edu]
- [interruptions.net]
- DBLP
Other Repositories/Bibliography
| Citations: | 161 - 17 self |
BibTeX
@INPROCEEDINGS{Latoza06maintainingmental,
author = {Thomas D. Latoza},
title = {Maintaining Mental Models: A Study of Developer Work Habits},
booktitle = {},
year = {2006},
pages = {492--501},
publisher = {ACM}
}
Share
 |
 |
 |
 |
||
OpenURL
Abstract
To understand developers ’ typical tools, activities, and practices and their satisfaction with each, we conducted two surveys and eleven interviews. Many problems arose from developers forced to invest great effort recovering implicit knowledge by exploring code and interrupting teammates only to persist this knowledge in their memory. Contrary to expectations that email and IM prevent expensive task switches caused by face-to-face interruptions, we found that face-to-face communication enjoys many advantages. Contrary to expectations that documentation makes understanding design rationale easy, we found that current design documents are inadequate. Contrary to expectations that code duplication involves the copy and paste of code snippets, developers reported several types of duplication. We use data to characterize these and other problems and draw implications for the design of tools for their solution.
Keyphrases
mental model developer work habit code snippet current design document developer typical tool implicit knowledge face-to-face communication face-to-face interruption eleven interview understanding design rationale several type great effort many advantage many problem interrupting teammate expensive task switch code duplication
