Artificial intelligence (AI) and machine learning (ML) are increasingly broadly adopted in
industry. However, based on well over a dozen case studies, we have learned that …

Technical debt, a metaphor for the long-term consequences of weak software development,
must be managed to keep it under control. The main goal of this article is to identify and …

The technical debt metaphor is widely used to encapsulate numerous software quality
problems. The metaphor is attractive to practitioners as it communicates to both technical …

Throughout a software development life cycle, developers knowingly commit code that is
either incomplete, requires rework, produces errors, or is a temporary workaround. Such …

Technical debt is a metaphor to describe the situation in which long-term code quality is
traded for short-term goals in software projects. Recently, the concept of self-admitted …

It is widely believed that refactoring improves software quality and developer productivity.
However, few empirical studies quantitatively assess refactoring benefits or investigate …

Technical debt is a metaphor introduced by Cunningham to indicate" not quite right code
which we postpone making it right". Examples of technical debt are code smells and bug …

Technical debt (TD) is a metaphor for taking shortcuts or workarounds in technical decisions
to gain short-term benefit in time-to-market and earlier software release. In this study, one …

Technical debt is a metaphor for delayed software maintenance tasks. Incurring technical
debt may bring short-term benefits to a project, but such benefits are often achieved at the …

The management of technical debt ultimately requires decision making-about incurring,
paying off, or deferring technical debt instances. This position paper discusses several …