From work to word: How do software developers describe their work?
Authors:
- 1 May 2009
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 21601852,p. 121-130
Abstract
Developers take notes about their work sessions, either to remember the work status and share it with collaborators, or because employers explicitly require this for project management matters. We report on an exploratory study which aims at understanding how software developers describe their work. We analyzed more than 750,000 work descriptions of about 2,000 professionals taken over 8 years in three settings. We observed several similarities in the content and time meta-data of work descriptions. Most frequent terms, such as top-30 performed activities, are used consistently. Particular templates such as ldquoACTION concerning ARTIFACT because of CAUSErdquo occur frequently. Developers described sessions that last 30-120 min. 4-16 times a day. Maintaining diaries seems to consume between 3-6% of the total work time, and in 10% of the sessions, developers did not describe their work in sufficient detail. We argue that our results make the first step towards automatically generating work diaries for software developers.Keywords
This publication has 16 references indexed in Scilit:
- Potentials and challenges of recommendation systems for software development2008
- What's a Typical Commit? A Characterization of Open Source Software Repositories2008
- Information Needs in Collocated Software Development Teams2007
- Using task context to improve programmer productivity2006
- How are Java software developers using the Eclipse IDE?IEEE Software, 2006
- Maintaining mental models2006
- No task left behind?2005
- Identifying reasons for software changes using historic databases2000
- People, organizations, and process improvementIEEE Software, 1994
- The diary study1993