Refactoring is a huge part of the programming workflow. Over the past year there has been a resurgence of the refactoring practice. With so much emphasis on the process and techniques of refactoring, the bigger picture is often missed.
When you refactor, you should stop and ask: "Why do I need to do this? What's different now? Did a perception change, was something missed, etc.? How can I prevent this the next time?"
Remember, not all smells are "bad" and it's a subjective scale.
This talk will cover (with code samples):
- Basics of refactoring
- Why refactorings are code smells
- How to adjust to these code smells to cook up something aromatic
- Some smells are stinkier than others
- Sometimes you just need an open flame
- Stop and smell the roses (when you can't avoid the smells)