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 …

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 …

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 …

Context Smells in software systems impair software quality and make them hard to maintain
and evolve. The software engineering community has explored various dimensions …

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 …

Context: Code smells are assumed to indicate bad design that leads to less maintainable
code. However, this assumption has not been investigated in controlled studies with …

Antipatterns are poor design choices that are conjectured to make object-oriented systems
harder to maintain. We investigate the impact of antipatterns on classes in object-oriented …

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 are poor implementation choices applied by developers during software
evolution that often lead to critical flaws or failure. Much in the same way, community smells …