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 …

Fowler et al. identified 22 Code Bad Smells to direct the effective refactoring of code. These
are increasingly being taken up by software engineers. However, the empirical basis of …

Context Code smells are suboptimal design or implementation choices made by
programmers during the development of a software system that possibly lead to low code …

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 …

In the last decade several catalogues have been defined to characterize bad code smells,
ie, symptoms of poor design and implementation choices. On top of such catalogues …

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 …

There is growing empirical evidence that some (patterns of) code smells seem to be, either
deliberately or not, ignored. More importantly, there is little knowledge about the factors that …

Context. In recent years, smells, also referred to as bad smells, have gained popularity
among developers. However, it is still not clear how harmful they are perceived from the …

Context: Code smells are associated to poor design and programming style, which often
degrades code quality and hampers code comprehensibility and maintainability. Goal …

Context: In this paper, we investigate how developers discuss code smells and anti-patterns
across three technical Stack Exchange sites. Understanding developers perceptions of …