Do practitioners intentionally self-fix Technical Debt and why?
Jie Tan, Daniel Feitosa, Paris Avgeriou

TL;DR
This study investigates whether software practitioners intentionally self-fix technical debt, revealing that most do so consciously, influenced by experience and responsibility, with decisions balancing costs and benefits.
Contribution
It provides empirical evidence from a survey showing practitioners' intentionality and rationales behind self-fixing technical debt in open-source projects.
Findings
Most practitioners consciously self-fix technical debt.
Higher experience correlates with increased concern for self-fixing.
Sense of responsibility influences self-fixing decisions.
Abstract
The impact of Technical Debt (TD) on software maintenance and evolution is of great concern, but recent evidence shows that a considerable amount of TD is fixed by the same developers who introduced it; this is termed self-fixed TD. This characteristic of TD management can potentially impact team dynamics and practices in managing TD. However, the initial evidence is based on low-level source code analysis; this casts some doubt whether practitioners repay their own debt intentionally and under what circumstances. To address this gap, we conducted an online survey on 17 well-known Java and Python open-source software communities to investigate practitioners' intent and rationale for self-fixing technical debt. We also investigate the relationship between human-related factors (e.g., experience) and self-fixing. The results, derived from the responses of 181 participants, show that a…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsSoftware Engineering Research · Open Source Software Innovations · Software Engineering Techniques and Practices
