Long method smell
From CSSEMediaWiki
(Difference between revisions)
(New page: "Object programs live best and longest with short methods. The payoffs of indirection - explanation, sharing and choosing - are supported by little methods. Everybody knows short is good."...) |
|||
| Line 1: | Line 1: | ||
| − | "Object programs live best and longest with short methods. The payoffs of indirection - explanation, sharing and choosing - are supported by little methods. Everybody knows short is good." | + | "Object programs live best and longest with short methods. The payoffs of indirection - explanation, sharing and choosing - are supported by little methods. Everybody knows short is good." --[[http://sis36.berkeley.edu/projects/streek/agile/bad-smells-in-code.html#Long+Method Bad Smells]] |
| + | |||
The Long method smell is a sign that you possibly need to take some part of your method and seperate it into another method. This action is known as the Extract Method | The Long method smell is a sign that you possibly need to take some part of your method and seperate it into another method. This action is known as the Extract Method | ||
Revision as of 04:47, 29 July 2008
"Object programs live best and longest with short methods. The payoffs of indirection - explanation, sharing and choosing - are supported by little methods. Everybody knows short is good." --[Bad Smells]
The Long method smell is a sign that you possibly need to take some part of your method and seperate it into another method. This action is known as the Extract Method
