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 …

The accuracy reported for code smell-detecting tools varies depending on the dataset used
to evaluate the tools. Our survey of 45 existing datasets reveals that the adequacy of a …

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 …

As social as software engineers are, there is a known and established gender imbalance in
our community structures, regardless of their open-or closed-source nature. To shed light on …

Software vulnerabilities are weaknesses in source code that can be potentially exploited to
cause loss or harm. While researchers have been devising a number of methods to deal …

Software engineering is now more than ever a community effort. Its success often weighs on
balancing distance, culture, global engineering practices and more. In this scenario many …

Code review is a software quality assurance practice widely employed in both open source
and commercial software projects to detect defects, transfer knowledge and encourage …

Code smells are indicators of potential problems in software. They tend to have a negative
impact on software quality. Several studies use machine learning techniques to detect bad …

Context: Social debt describes the accumulation of unforeseen project costs (or potential
costs) from sub-optimal software development processes. Community smells are …

Code smells are symptoms of poor implementation choices applied during software
evolution. While previous research has devoted effort in the definition of automated solutions …