Maintaining mental models

Thomas D. LaToza, Gina Venolia, Robert DeLine

2006 · 616 citations · 14 references

Concepts

TL;DR

The study surveyed and interviewed developers to understand their typical tools, activities, practices, and satisfaction levels. The authors collected survey and interview data, then analyzed it to characterize problems and derive implications for tool design. The study revealed that developers expend substantial effort recovering implicit knowledge, rely on memory, value face‑to‑face communication, find documentation inadequate, and encounter diverse forms of code duplication, highlighting gaps for tool improvement.

Abstract

To understand developers' typical tools, activities, and practices and their satisfaction with each, we conducted two surveys and eleven interviews. We found that many problems arose because developers were forced to invest great effort recovering implicit knowledge by exploring code and interrupting teammates and this knowledge was only saved 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.

References

14