Context The concept of technical debt (TD) contextualizes problems faced during software
evolution considering the tasks that are not carried out adequately during its development …

Technical Debt is a metaphor used to express sub-optimal source code implementations
that are introduced for short-term benefits that often need to be paid back later, at an …

The metaphor of technical debt was introduced to express the trade off between productivity
and quality, ie, when developers take shortcuts or perform quick hacks. More recently, our …

Technical debt refers to the phenomena of taking shortcuts to achieve short term gain at the
cost of higher maintenance efforts in the future. Recently, approaches were developed to …

Technical debt (TD) is a metaphor to describe the situation where developers introduce
suboptimal solutions during software development to achieve short-term goals that may …

Keeping track of and managing Self-Admitted Technical Debts (SATDs) are important to
maintaining a healthy software project. This requires much time and effort from human …

Context Previous work has shown that one can explore code comments to detect Self-
Admitted Technical Debt (SATD) using a contextualized vocabulary. However, current …

Standard software analytics often involves having a large amount of data with labels in order
to commission models with acceptable performance. However, prior work has shown that …

Self-admitted technical debt (SATD) refers to a specific type of technical debt that is
introduced intentionally in the software development and maintenance processes. SATD …

Abstract Context: Self-Admitted Technical Debt (SATD) refers to the technical debt in
software that is explicitly flagged, typically by the source code comment. The SATD literature …