Refactoring and smells have been well researched by the software-engineering research
community these past decades. Several secondary studies have been published on code …

Code smells in a program represent indications of structural quality problems, which can be
addressed by software refactoring. However, refactoring intends to achieve different goals in …

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 …

Code smells tend to compromise software quality and also demand more effort by
developers to maintain and evolve the application throughout its life-cycle. They have long …

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 …

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 Reusing a design pattern is not always in the favor of developers. Thus, the code
starts smelling. The presence of “Code Smells” leads to more difficulties for the developers …

Previous studies have investigated the reasons behind refactoring operations performed by
developers, and proposed methods and tools to recommend refactorings based on quality …

Code smells, ie, symptoms of poor design and implementation choices applied by
programmers during the development of a software project [2], represent an important factor …