Awareness of design smells – indicators of common design problems – helps developers or software engineers understand mistakes made while designing, what design principles were overlooked or misapplied, and what principles need to be applied properly to address those smells through refactoring. Developers and software engineers may "know" principles and patterns, but are not aware of the "smells" that exist in their design because of wrong or mis-application of principles or patterns. These smells tend to contribute heavily to technical debt – further time owed to fix projects thought to be complete – and need to be addressed via proper refactoring.<br><br><i>Refactoring for Software Design Smells</i> presents 25 structural design smells, their role in identifying design issues, and potential refactoring solutions. Organized across common areas of software design, each smell is presented with diagrams and examples illustrating the poor design practices and the problems that result, creating a catalog of nuggets of readily usable information that developers or engineers can apply in their projects. The authors distill their research and experience as consultants and trainers, providing insights that have been used to improve refactoring and reduce the time and costs of managing software projects. Along the way they recount anecdotes from actual projects on which the relevant smell helped address a design issue.<ul><li>A comprehensive catalogue of structural design smells and their refactoring solutions to solve problems occurring in design</li><li>Explains the importance of smells in managing technical debt, an area of increased concern at software engineering conferences</li><li>Each smell includes examples, source code, and visualization diagrams to facilitate understanding</li><li>Describes solutions across common software design concepts and smells that cross multiple domains</li></ul>