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 …

Code comments are a primary means to document source code. Kee** comments up-to-
date during code change activities requires substantial time and attention. For this reason …

Technical debt is a metaphor indicating sub-optimal solutions implemented for short-term
benefits by sacrificing the long-term maintainability and evolvability of software. A special …

Self-admitted technical debt (SATD) is a particular case of Technical Debt (TD) where
developers explicitly acknowledge their sub-optimal implementation decisions. Previous …

Background. Self-admitted technical debt (SATD) is a special kind of technical debt that is
intentionally introduced and remarked by code comments. Those technical debts reduce the …

Code intelligence tools such as GitHub Copilot have begun to bridge the gap between
natural language and programming language. A frequent software development task is the …

Kee** 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 …

This paper provides a starting point for Software Engineering (SE) researchers and
practitioners faced with the problem of training machine learning models on small datasets …

There is a trend of researchers and practitioners to directly apply pre-trained models to solve
their specific tasks. For example, researchers in software engineering (SE) have …

Abstract Self-Admitted Technical Debt (SATD) is primarily studied in Object-Oriented (OO)
languages and traditionally commercial software. However, scientific software coded in …