# Unhappy Developers: Bad for Themselves, Bad for Process, and Bad for Software Product

## TL;DR

This study explores how developer unhappiness negatively impacts individual well-being, development processes, and software quality, highlighting the importance of fostering positive emotions in software engineering.

## Contribution

First qualitative analysis identifying 49 consequences of developer unhappiness, providing a new classification scheme to guide future happiness research and management practices.

## Key findings

- Unhappiness affects developers' well-being and productivity.
- Unhappiness impacts software development processes and outcomes.
- The study introduces a classification scheme for consequences of unhappiness.

## Abstract

Recent research in software engineering supports the "happy-productive" thesis, and the desire of flourishing happiness among programmers is often expressed by industry practitioners. Recent literature has suggested that a cost-effective way to foster happiness and productivity among workers could be to limit unhappiness of developers due to its negative impact. However, possible negative effects of unhappiness are still largely unknown in the software development context. In this paper, we present the first results from a study exploring the consequences of the unhappy developers. Using qualitative data analysis of the survey responses given by 181 participants, we identified 49 potential consequences of unhappiness while developing software. These results have several implications. While raising the awareness of the role of moods, emotions and feelings in software development, we foresee that our classification scheme will spawn new happiness studies linking causes and effects, and it can act as a guideline for developers and managers to foster happiness at work.