Refactoring

RefactoringImproving The Design of Existing Code

Reporter：Jiayun Zhou <[email protected]>

Date ：2011/07/13

Outline

Introduction

Bad Smells & Refactorings

Conclusion

Copyright by IISI. All rights reserved 2

Introduction

Eclipse 1.0 – Nov 2001


Eclipse 2.0 – Jun 2002


Eclipse 2.1 – Mar 2003


Eclipse 3.7 – Jun 2011


Martin Fowler


Kent Beck


Bad Smells & Refactorings

Bad Smell

If it stinks, change it.

-Grandma Beck,discussing child-rearing philosophy


WTF


What the Fxxk


Good Programmer

• 30% Good Habits

• 30% English

• 40% Passion, Talent, Practice, and Everything Else


Duplicated Code (Bad Smell)

DRY

(Don't Repeat Yourself)


Duplicated Code (Bad Smell)

DRY

(Don't Repeat Yourself)

vs.

WET

(We Enjoy Typing)


Pull Up Method(Refactoring)


Pull Up – 1 (Eclipse)


Long Method (Bad Smell)

• Short methods are good

• Whenever we feel the need to comment something, we write a method instead

• Method name explains the intention


Extract Method(Refactoring)


Extract Method – 1 (Eclipse)


Conditionals and loops also give signs for extractions.

Use Decompose Conditional to deal with conditional expressions.

With loops, extract the loop and the code within the loop into its own method.


Large Class (Bad Smell)

• Trying to do too much

• Shows up as too many instance variables

• Duplicated code cannot be far behind


Extract Class(Refactoring)


Extract Class – 1 (Eclipse)


Long Parameter List(Bad Smell)

• Hard to understand

• Become inconsistent and difficult to use

• Forever changing them as you need more data


Replace Parameter with Method (Refactoring)


Preserve Whole Object(Refactoring)


Introduce Parameter Object(Refactoring)


Introduce Parameter Object –01 (Eclipse)


Comments (Bad Smell)

• They are sweet smell

• Don't use as a deodorant


Conclusion

How to refactor safely?


Unit Test


Ｈow about the translation?


中譯

你可以選擇每個 class 和函式的名字，這給了你一個解釋自己意圖的機會。class 或函式內部則解釋實現這個意圖的作法。如果class 和函式內部又以「更小單元的意圖」來編寫，你所寫的程式碼就可以「與其結構中的大部分重要資訊溝通」。 (p.61)


原文

Choosing the name of each class and the name of each method gives you an opportunity to explain what you intend. The internals of the class or method explain how the intention is realized. If the internals also are written in terms of intention in yet smaller pieces, you can write code that communicates most of the important information about its own structure.


我的翻譯

你可以選擇每個 class 和函式的名字，這給了你一個解釋自己意圖的機會。class 或函式內部則解釋實現這個意圖的作法。如果class 和函式內部又以「更小單元的意圖」來編寫，你所寫的程式碼就可以「表達出它自己結構的大部分重要資訊」。


盡信書不如無書


琴鍵有限，琴藝無限


Headquarter

6F., No.7, Sec. 2, Xianmin Blvd., Banqiao Dist., New Taipei City 22041, Taiwan(R.O.C.)

TEL : +886-2-8969-1969 FAX : +886-2-8969-3359

- Thank You -

Refactoring

Technology

Transcript of Refactoring