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 …

Context Identifying refactoring opportunities in object-oriented code is an important stage
that precedes the actual refactoring process. Several techniques have been proposed in the …

Code smells are symptoms of poor design and implementation choices that may hinder
code comprehension, and possibly increase changeand fault-proneness. While most of the …

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 represent symptoms of poor implementation choices. Previous studies found
that these smells make source code more difficult to maintain, possibly also increasing its …

Infrastructure as Code (IaC) is the practice of specifying computing system configurations
through code, and managing them through traditional software engineering methods. The …

One of the most widely used techniques to improve the quality of existing software systems
is refactoring—the process of improving the design of existing code by changing its internal …

The presence of code smells will increase the risk of failure, make software difficult to
maintain, and introduce potential technique debt in the future. Although many deep-learning …

Context Code smells are patterns in source code associated with an increased defect rate
and a higher maintenance effort than usual, but without a clear definition. Code smells are …

A broken snapshot represents a snapshot from a project's change history that cannot be
compiled. Broken snapshots can have significant implications for researchers, as they could …