Hidden in Plain Sight: Where Developers Confess Self-Admitted Technical Debt

TL;DR

This study links self-admitted technical debt comments to specific code constructs in Java OSS, revealing their common locations and suggesting they reflect developer awareness rather than neglect.

Contribution

It connects SATD comments with surrounding code structures at scale, providing insights into their typical locations and implications.

Findings

SATD mainly occurs near definitions, conditionals, and exception handling.

Developers use SATD as an intentional signal of awareness.

Over 225,000 SATD comments linked to source code.

Abstract

Context. Detecting Self-Admitted Technical Debt (SATD) is crucial for proactive software maintenance. Previous research has primarily targeted detecting and prioritizing SATD, with little focus on the source code afflicted with SATD. Our goal in this work is to connect the SATD comments with source code constructs that surround them. Method. We leverage the extensive SATD dataset PENTACET, containing code comments from over 9000 Java Open Source Software (OSS) repositories. We quantitatively infer where SATD most commonly occurs and which code constructs/statements it most frequently affects. Results and Conclusions. Our large-scale study links over 225,000 SATD comments to their surrounding code, showing that SATD mainly arises in inline code near definitions, conditionals, and exception handling, where developers face uncertainty and trade-offs, revealing it as an intentional signal of awareness during change rather than mere neglect.