Profiling Developers Through the Lens of Technical Debt

by   Zadia Codabux, et al.

Context: Technical Debt needs to be managed to avoid disastrous consequences, and investigating developers' habits concerning technical debt management is invaluable information in software development. Objective: This study aims to characterize how developers manage technical debt based on the code smells they induce and the refactorings they apply. Method: We mined a publicly-available Technical Debt dataset for Git commit information, code smells, coding violations, and refactoring activities for each developer of a selected project. Results: By combining this information, we profile developers to recognize prolific coders, highlight activities that discriminate among developer roles (reviewer, lead, architect), and estimate coding maturity and technical debt tolerance.


page 5

page 6


The use of incentives to promote Technical Debt management

When developing software, it is vitally important to keep the level of t...

Gamification: a Game Changer for Managing Technical Debt? A Design Study

Context: Technical debt management is challenging for software engineers...

On Relating Technical, Social Factors, and the Introduction of Bugs

As collaborative coding environments make it easier to contribute to sof...

Does Migrate a Monolithic System to Microservices Decreases the Technical Debt?

Background. The migration from monolithic systems to microservices invol...

Profiling Software Developers with Process Mining and N-Gram Language Models

Context: Profiling developers is challenging since many factors, such as...

UX Debt: Developers Borrow While Users Pay

Technical debt has become a well-known metaphor among software professio...

How Interaction Designers Use Tools to Manage Ideas

This paper presents a grounded theory-analysis based on a qualitative st...