Analyzing The Impact Of Feedback In GitHub On The Software Developer's Mood

Abstract

Software development depends on cooperation between people, and the way it works can define the future of the software project. Developers emotions affect their productivity and way they work, yet there is little information about how developers can influence the mood of each other. As a first step toward understanding how feedback may affect the developers' sentiment, this paper analyzes the mood variations on more than 78k pull requests and 268k pull comments on GitHub. We found that in 31.16% of the cases the developers presented a significant mood variation within one hour when receiving feedback on their pull requests. The variation reduces to 18.16% when evaluating one day before and after the commentary. In software projects with less than 34k lines of code, the number of developers that never contribute again after receiving a negative comment on the first pull request is 10.97%; this number more than doubles to 24.02% when evaluating projects with more than 197k lines of code.

Modern Code Reviews—Survey of Literature and Practice

“…Similarly, a very large study found that negative feedback has a significant impact on developers' attitude [215]. Developers might not contribute again after receiving negative feedback and this impact increases with the size of the project [215]. 4.2.4 CRP -Modern code review process properties.…”

“…Specific feedback such as "Incomplete fix" and "Suboptimal solution" might encourage contributors to continue to work in open source software projects [185]. Similarly, a very large study found that negative feedback has a significant impact on developers' attitude [215]. Developers might not contribute again after receiving negative feedback, and this impact increases with the size of the project [215].…”

Modern code reviews - Preliminary results of a systematic mapping study

“…Team Performance [65] Socio-Technical modern code review metrics Identification of bugs/warning/vulnerabilities [44] Reviewers' path development experience Identification of bugs/warning/vulnerabilities [79] Feedback Developers' sentiment [64] quality [7,43,46,66,76], human memory [39,70], chances in inducing bug fixes [7], if-statements and change requests [59,83,84], and the identification of bugs/warning/vulnerabilities [12,54].…”