Refactoring – the strategies for making disciplined changes to programs – are like mini architectures themselves. They are architectures of strategies of how to get from one design – to another – safely.
Just like design patterns, they have motivating forces, are dependent on context, and many are defined in terms of the nature/terminology of object-oriented programming.
Eclipse and several other very popular IDEs for Java have included a bunch of commands to do some of the very refactorings described in this book.
It is invaluable to read it. Learn both the refactorings themselves – and the spirit for why, when, and where to do them – not just how.
Being able to change software is just as important as being able to design good software in the first place. Nothing of great size created over a long time just comes together perfectly.
Major course adjustments as well as fine-tuning are required from time to time. This book will make you an expert at carrying out those adjustments.
If you are programming in Java and using Eclipse then you really need to read this book to get the most out of your powerful IDE.
One thing that will catch your eye as you look through this book is that a lot of refactorings have exact opposites. That should tell you right there that simply being able to do a refactoring is not enough.
You also need the knowledge/wisdom to know which way you need to go, and if the code you are regarding is in the better state already. No sense changing the same piece of code back and forth forever! Refactor wisely.
Refactoring as a way to improve code and learn OO Programming — 1 year ago