2015 IEEE 23rd International Conference on Program Comprehension 2015
DOI: 10.1109/icpc.2015.12
|View full text |Cite
|
Sign up to set email alerts
|

I Know What You Did Last Summer - An Investigation of How Developers Spend Their Time

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

2
94
0
3

Year Published

2016
2016
2022
2022

Publication Types

Select...
3
3
2

Relationship

0
8

Authors

Journals

citations
Cited by 143 publications
(99 citation statements)
references
References 28 publications
2
94
0
3
Order By: Relevance
“…As an example, Goncalves and colleagues found in their observations and interviews that developers spend 45% of their time collaborating, 32% for seeking information, and they only use software process tools during 9% of their time [23]. More recent studies by Minelli et al [12] and Amann et al [13] focused on how developers spend their time inside the IDE.…”
Section: Developers' Work Practicesmentioning
confidence: 99%
See 1 more Smart Citation
“…As an example, Goncalves and colleagues found in their observations and interviews that developers spend 45% of their time collaborating, 32% for seeking information, and they only use software process tools during 9% of their time [23]. More recent studies by Minelli et al [12] and Amann et al [13] focused on how developers spend their time inside the IDE.…”
Section: Developers' Work Practicesmentioning
confidence: 99%
“…Other studies have focused on how developers spend their time inside the Integrated Development Environment (IDE) (e.g., [12], [13]). The industry has also seen an increasing trend with self-monitoring tools to track activity and work habits, with applications such as RescueTime [14] or Codealike [15].…”
Section: Ko Et Al Observed Software Developers To Determine Whatmentioning
confidence: 99%
“…Predominantly, each of these approaches focuses on supporting one specific activity during the work on a change task to determine relevant information without adapting to the various activities the developer is performing over the course of the change task. With the wide variety of developer activities during a change task [2], [4] and change tasks lasting anywhere from a few minutes to several days [5], finding the right approach and the relevant information as well as switching to it is difficult at best [6], [7]. The more we know about developers' activities during change tasks, the better we can support them in their work.…”
Section: Introductionmentioning
confidence: 99%
“…Another aspect to consider when looking at the impact of software maintenance concerns the time needed to understand systems by developers. Several studies estimate program comprehension to take more than half the time spent on maintenance [ZSG79,MML15]. These two factors combined together highlight that getting an understanding of systems impacts for 30 to 50% of the overall costs [FH82].…”
Section: A Genesis Of Rssesmentioning
confidence: 99%
“…A deeper exploration of the developer interaction, in particular in the IDE might be beneficial for the recommendation engine in general. For example, Minelli et al [MML15] track events in the IDE, identifying when the developer enters the "understanding" phase or navigate the code. Such information can be leveraged to refine the informational context of the developer (on the IDE side), and select the best moment when to fire a notification.…”
Section: Leveraging Developers Interactionmentioning
confidence: 99%