Background: Code smells indicate suboptimal design or implementation choices in the
source code that often lead it to be more change-and fault-prone. Researchers defined …

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 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 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 …

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

Current approaches to program synthesis with Large Language Models (LLMs) exhibit a"
near miss syndrome": they tend to generate programs that semantically resemble the correct …

Test smells are defined as sub-optimal design choices developers make when
implementing test cases. Hence, similar to code smells, the research community has …

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 …

Code smells represent poor implementation choices performed by developers when
enhancing source code. Their negative impact on source code maintainability and …

Code smells are structures in code that often harm its quality. Manually detecting code
smells is challenging, so researchers proposed many automatic detectors. Traditional code …