Identifying Code Smells
summary
Catalogues 21 code smells and walks through concrete Java code examples for each category (bloaters, OO abusers, change preventers, dispensables, couplers), pointing to the exact lines that make a method or class problematic and when a smell is merely cosmetic. Offers a GitHub repo with the example snippets, cites the Refactoring catalog and Refactoring Guru for fixes, and warns that actual refactoring is a multi‑hour exercise rather than a one‑slide solution.
AI-written summary · about
chapters (9)
- 0:00Welcome
- 3:22Code smells defined
- 5:54Code smell taxonomy
- 6:14Bloaters explained
- 13:27Object-oriented programming abusers category
- 19:23Change preventors
- 24:03Dispensables overview
- 28:47Couplers examples
- 33:31Addressing code smells
related talks
36mRuby Smells
01h 00mPhantastic Code Smells and where to find them
44mRefactoring Legacy Code Guided by Simple Design
52mMeasuring code quality in WTFs per minute
33mBuilding Code Quality
47mAnti-patterns and smells in test automation
23mClean Architecture? Clean Code? Refactoring? Tests? What does this change in my code?
46mDirty Tests and How to Clean Them