Does your Design Smell
summary
Cites a study that attributes 64% of defects to design and offers a catalog of 25 smells with causes and refactor recipes. Calls out concrete smells: classes with many public fields, a “god” class example with 498 incoming dependencies and 71 outgoing, and collection misuse (using Vector/Stack wrong). Lists detection options — some C# detectors, metric tools and a Java tool transcribed as Ifusion — but notes many smells remain undetectable by current tools.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 5:29Design smells explained
- 10:06Public field problems
- 13:17Broken inheritance example
- 15:28Detecting and fixing smells
- 16:52Limitations of current tools
related talks
55mIdentifying Common Code Smells (In C++)
30mYour Code Stinks and You Didn't Even Know
59mC++ Code Smells
56mClean Code, Two Decades Later
01h 01mSoftware Design: Myths and Legends
56mIdentifying Common Code Smells
01h 15mHow to measure your architecture
20mFind Out If Your Design System Is Better Than Nothing