 | 2011 |
| 9 |  | Thomas D. LaToza,
Brad A. Myers:
Designing useful tools for developers.
PLATEAU 2011: 45-50 |
| 8 |  | Thomas D. LaToza,
Brad A. Myers:
Visualizing call graphs.
VL/HCC 2011: 117-124 |
| 7 |  | Cyrus Omar,
YoungSeok Yoon,
Thomas D. LaToza,
Brad A. Myers:
Active code completion.
VL/HCC 2011: 261-262 |
| 2010 |
| 6 |  | Thomas D. LaToza,
Brad A. Myers:
Developers ask reachability questions.
ICSE (1) 2010: 185-194 |
| 2008 |
| 5 |  | Thomas D. LaToza:
Answering common questions about code.
ICSE Companion 2008: 983-986 |
| 4 |  | Thomas D. LaToza:
Answering control flow questions about code.
OOPSLA Companion 2008: 921-922 |
| 2007 |
| 3 |  | Thomas D. LaToza,
David Garlan,
James D. Herbsleb,
Brad A. Myers:
Program comprehension as fact finding.
ESEC/SIGSOFT FSE 2007: 361-370 |
| 2006 |
| 2 |  | Thomas D. LaToza,
Gina Venolia,
Robert DeLine:
Maintaining mental models: a study of developer work habits.
ICSE 2006: 492-501 |
| 1 |  | Thomas D. LaToza:
Using architecture to change code: studying information needs.
OOPSLA Companion 2006: 764-765 |