Code smells are symptoms of poor design and implementation choices weighing heavily on
the quality of produced source code. During the last decades several code smell detection …

Code smells are structural characteristics of software that may indicate a code or design
problem that makes software hard to evolve and maintain, and may trigger refactoring of …

Code smells were defined as symptoms of poor design choices applied by programmers
during the development of a software project [2]. They might hinder the comprehensibility …

Technical debt is a metaphor introduced by Cunningham to indicate “not quite right code
which we postpone making it right”. One noticeable symptom of technical debt is …

Code smells are structures in the source code that suggest the possibility of refactorings.
Consequently, developers may identify refactoring opportunities by detecting code smells …

Antipatterns are" poor" solutions to recurring design problems which are conjectured in the
literature to make object-oriented systems harder to maintain. However, little quantitative …

We investigate the relationship between faults and five of Fowler et al.'s least-studied smells
in code: Data Clumps, Switch Statements, Speculative Generality, Message Chains, and …

Code smells represent poor implementation choices performed by developers when
enhancing source code. Their negative impact on source code maintainability and …

Code smells are particular patterns in object-oriented systems that are perceived to lead to
difficulties in the maintenance of such systems. It is held that to improve maintainability, code …

Bad smells are sub-optimal code structures that may represent problems needing attention.
We conduct an extensive literature review on bad smells relying on a large body of …