In general, I think the ability to recognize code smells boils down to Knowledge, Understanding, and Practice. You have to know what you are looking for and understand the implications of what you see when it's there. Only practice, and lots of it, will allow you to effectively deal with problems that you detect though.
Still, it's a good question. If the book has any specific discussion around code smells and how to deal with them, I'd be interested to know what they are.
As Chris mentions in another post reply - running sonarqube on your code base will tell you a lot -
give a starting point...
Very long methods always disturb me ;-) Especially when I need to scroll up/down while reading it...
Also another thing that usually stands is the violation of compose method Duplication is also an ever present evil - Almost every code base I have worked with (including mine too at times ;-)
- this duplication beast kind of creeps in so stealthily... But the easiest to attack IMHO...
Politics is a circus designed to distract you from what is really going on. So is this tiny ad:
Free, earth friendly heat - from the CodeRanch trailboss