Software Engineering discussion

It is tough task to cover the breadth of refactoring techniques listed in this chapter without code examples. Fowler's book is the classic reference for this. I am glad that this chapter covers the "When should I refactor?" question. I think that it should have also addressed the "When should I stop refactoring?" question too, because polishing code while striving for perfection can continue forever.

Nice chapter that I can use as a quick reference to refactoring…may be...

Many sources on refactoring, including this chapter, reference Fowler’s Refactoring book. So, I decided to purchase it and found Fowler’s Refactoring web-site with nice catalog of Refactoring suggestions with examples and graphics:

http://www.refactoring.com/catalog/in....

http://www.refactoring.com/catalog/in...

I agree this chapter had some good check lists and classifications of refactoring.

It seemed very pro-refactoring. Sometimes refactoring just isn't worth the cost. My managers never schedule refactoring projects (or iterations), because by definition they have no imediate value-add to the customers.