Long method smell
From CSSEMediaWiki
(Difference between revisions)
| 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." --[http://sis36.berkeley.edu/projects/streek/agile/bad-smells-in-code.html#Long+Method Bad Smells] | "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 code 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 [http://www.refactoring.com/catalog/extractMethod.html Extract Method] | The Long method code 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 [http://www.refactoring.com/catalog/extractMethod.html Extract Method] | ||
Revision as of 04:53, 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 code 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
