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 …

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 …

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 …

In past and recent years, the issues related to managing technical debt received significant
attention by researchers from both industry and academia. There are several factors that …

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 …

By now you have a good idea of how refactoring works. But just because you know how
doesn't mean you know when. Deciding when to start refactoring, and when to stop, is just …

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 …

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 …

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 …