Code Smells or Code Screams?
According to Joshua Kerievsky
Code Smells identify frequently occurring design problems in a way that is more specific or targeted than general design guidelines (like “loosely coupled code” or “duplication-free code”).
The term Code Smell was originally coined by Kent Beck and Martin‘s Refactoring book made it really big. I completely dig the whole “Smell” analogy.
But of late, Sandeep and I’ve been thinking on lines of Code Screams. Code Smells seems a little subtle to me. The Scream analogy goes inline with “Listen to your Code” advice. Also as Nick pointed out, if you ignore Code Screams for a while, you might go deaf!
