Wely Lau

If you like to write well-managed and proper code, I strongly advice you take a look at this good stuff. This whitepaper was prepared by Sean Chambers and Simone Chiaretta. But of course, most material refers to the refactoring.com, that managed by Mr Refactoring, Martin Fowler.
Thanks to Zeddy to share us this information through dotnet mailing list.

The followings are the list of the refactoring techniques that you will find:

• Refactoring Day 1 : Encapsulate Collection
• Refactoring Day 2 : Move Method
• Refactoring Day 3 : Pull Up Method
• Refactoring Day 4 : Push Down Method
• Refactoring Day 5 : Pull Up Field
• Refactoring Day 6 : Push Down Field
• Refactoring Day 7 : Rename (method, class, parameter)
• Refactoring Day 8 : Replace Inheritance with Delegation
• Refactoring Day 9 : Extract Interface
• Refactoring Day 10 : Extract Method
• Refactoring Day 11 : Switch to Strategy
• Refactoring Day 12 : Break Dependencies
• Refactoring Day 13 : Extract Method Object
• Refactoring Day 14 : Break Responsibilities
• Refactoring Day 15 : Remove Duplication
• Refactoring Day 16 : Encapsulate Conditional
• Refactoring Day 17 : Extract Superclass
• Refactoring Day 18 : Replace exception with conditional
• Refactoring Day 19 : Extract Factory Class
• Refactoring Day 20 : Extract Subclass
• Refactoring Day 21 : Collapse Hierarchy
• Refactoring Day 22 : Break Method
• Refactoring Day 23 : Introduce Parameter Object
• Refactoring Day 24 : Remove Arrowhead Antipattern
• Refactoring Day 25 : Introduce Design By Contract checks
• Refactoring Day 26 : Remove Double Negative
• Refactoring Day 27 : Remove God Classes
• Refactoring Day 28 : Rename boolean method
• Refactoring Day 29 : Remove Middle Man
• Refactoring Day 30 : Return ASAP
• Refactoring Day 31 : Replace conditional with Polymorphism

Why wait? Go and grab it now!

Share this post: | | | |