Code smells indicate problems in design or code which makes software hard to change and
maintain. It has become a sign of software systems that cause complications in maintaining …

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

Technical debt is a metaphor to reflect the tradeoff software engineers make between short-
term benefits and long-term stability. Self-admitted technical debt (SATD), a variant of …

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 …

Code summarization, the task of generating useful comments given the code, has long been
of interest. Most of the existing code summarization models are trained and validated on …

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

Vulnerabilities publicly disclosed in the National Vulnerability Database (NVD) are assigned
with CVE (Common Vulnerabilities and Exposures) IDs and associated with specific …

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 …