ACM Home Page
Please provide us with feedback. Feedback
A sketch of the programmer's coach: making programmers more effective
Full text PdfPdf (496 KB)
Source
International Conference on Software Engineering archive
Proceedings of the 2008 international workshop on Cooperative and human aspects of software engineering table of contents
Leipzig, Germany
Pages 97-100  
Year of Publication: 2008
ISBN:978-1-60558-039-5
Authors
David C. Shepherd  University of British Columbia, Vancouver, BC, Canada
Gail C. Murphy  University of British Columbia, Vancouver, BC, Canada
Sponsors
ACM: Association for Computing Machinery
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 35,   Downloads (12 Months): 123,   Citation Count: 2
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1370114.1370139
What is a DOI?

ABSTRACT

As programmers work on source code, they ask an array of questions that are difficult to answer manually. To help answer these questions, programmers often employ software tools; often in attempting to use these tools, the programmers encounter many obstacles which frustrate their efforts and lead to less than optimal tool utilization. Possibly worse, programmers often intentionally under utilize available tools as they prefer to answer questions only with tools they have used before. We hypothesize that we can coach programmers towards a more systematic use of appropriate software tools that would enable the programmers to be more productive in the completion of their work. We propose to use activity logs collected automatically to deduce the questions a given programmer asks a frequently and then to coach the programmer automatically on appropriate, possibly unfamiliar, tools to answer those questions more effectively. By using activity logs to inform coaching decisions, our approach is based on an objective cost metric. We envision an environment that enables a programmer to learn how to use appropriate tools systematically.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
C. Artho. Jlint - find bugs in java programs. http://jlint.sourceforge.net/, 2006.
2
 
3
Oliver Burn. Checkstyle 4.4. http://checkstyle.sourceforge.net/index.html, 2008.
 
4
5
 
6
Gerhard Fischer. A critic for lisp. In IJCAI, pages 177--184, 1987.
7
 
8
Watts S. Humphrey. Introducing the personal software process. Ann. Software Eng., 1:311--325, 1995.
 
9
10
11
 
12
13
14
 
15
16
 
17


Collaborative Colleagues:
David C. Shepherd: colleagues
Gail C. Murphy: colleagues