• Publications
  • Influence
A large-scale empirical study of just-in-time quality assurance
TLDR
The findings indicate that “Just-In-Time Quality Assurance” may provide an effort-reducing way to focus on the most risky changes and thus reduce the costs of developing high-quality software. Expand
Are Bullies More Productive? Empirical Study of Affectiveness vs. Issue Fixing Time
TLDR
It is found that the happier developers are (expressing emotions such as JOY and LOVE in their comments), the shorter the issue fixing time is likely to be, and negative emotions, such as SADNESS, are linked with longerissue fixing time. Expand
The impact of code review coverage and code review participation on software quality: a case study of the qt, VTK, and ITK projects
TLDR
The results empirically confirm the intuition that poorly reviewed code has a negative impact on software quality in large systems using modern reviewing tools. Expand
Will my patch make it? And how fast? Case study on the Linux kernel
TLDR
This paper crosslinks and analyzes eight years of patch reviews from the kernel mailing lists and committed patches from the Git repository to understand which patches are accepted and how long it takes those patches to get to the end user. Expand
Do faster releases improve software quality? An empirical case study of Mozilla Firefox
TLDR
It is found that with shorter release cycles, users do not experience significantly more post-release bugs and bugs are fixed faster, yet users experience these bugs earlier during software execution (the program crashes earlier). Expand
On rapid releases and software testing: a case study and a semi-systematic literature review
TLDR
The changes in software testing effort after moving to rapid releases is investigated in the context of a case study on Mozilla Firefox, and a semi-systematic literature review shows that rapid releases are a prevalent industrial practice that are utilized even in some highly critical domains of software engineering. Expand
The Emotional Side of Software Developers in JIRA
TLDR
This paper manually labeled 2,000 issue comments and 4,000 sen-tences written by developers with emotions such as love,joy, surprise, anger, sadness and fear, allowing the investigation of the role of affects in software development. Expand
Co-evolution of Infrastructure and Source Code - An Empirical Study
TLDR
Through an empirical study of the version control system of 265 Open Stack projects, it is found that infrastructure files are large and churn frequently, which could indicate a potential of introducing bugs. Expand
An empirical study of the impact of modern code review practices on software quality
TLDR
Through a case study of the Qt, VTK, and ITK projects, it is found that code review coverage, participation, and expertise share a significant link with software quality. Expand
Do developers feel emotions? an exploratory analysis of emotions in software artifacts
TLDR
This study analyzes whether development artifacts like issue reports carry any emotional information about software development, a first step towards verifying the feasibility of an automatic tool for emotion mining in software development artifacts. Expand
...
1
2
3
4
5
...