When users become collaborators: towards continuous and context-aware user input
Proceedings of the 24th ACM SIGPLAN conference companion on Object oriented programming systems languages and applications
Assisting engineers in switching artifacts by using task semantic and interaction history
Proceedings of the 2nd International Workshop on Recommendation Systems for Software Engineering
An experience report on scaling tools for mining software repositories using MapReduce
Proceedings of the IEEE/ACM international conference on Automated software engineering
How do developers blog?: an exploratory study
Proceedings of the 8th Working Conference on Mining Software Repositories
Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work
Automatically detecting developer activities and problems in software development work
Proceedings of the 34th International Conference on Software Engineering
Proceedings of the 18th ACM conference on Innovation and technology in computer science education
Episode measurement method: a data collection technique for observing team processes
Proceedings of the 2013 International Conference on Software and System Process
The MSR cookbook: mining a decade of research
Proceedings of the 10th Working Conference on Mining Software Repositories
How do open source communities blog?
Empirical Software Engineering
Hi-index | 0.00 |
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 “ACTION concerning ARTIFACT because of CAUSE” 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.