Difference between revisions of "Refactor code"
Jump to navigation
Jump to search
m (terse/full) |
m (Typo.) |
||
Line 7: | Line 7: | ||
|so=Take every opportunity to eliminate redundant code and rewrite code, making it more elegant. | |so=Take every opportunity to eliminate redundant code and rewrite code, making it more elegant. | ||
|wish full=A small code base contains less bugs and is less effort to maintain. | |wish full=A small code base contains less bugs and is less effort to maintain. | ||
|background=Refactoring encompasses any changes to the system that leaves its behavior | |background=Refactoring encompasses any changes to the system that leaves its behavior unchanged while enhancing nonfunctional quality (i.e. simplicity, flexibility, understandability, or performance). | ||
|therefore full=Take every opportunity to eliminate redundant code and rewrite code, making it more elegant. | |therefore full=Take every opportunity to eliminate redundant code and rewrite code, making it more elegant. | ||
}} | }} |
Revision as of 10:05, 16 June 2013
…product development, completing product backlog items.
✣ ✣ ✣
A small code base contains less bugs and is less effort to maintain.
Refactoring encompasses any changes to the system that leaves its behavior unchanged while enhancing nonfunctional quality (i.e. simplicity, flexibility, understandability, or performance).
Therefore:
Take every opportunity to eliminate redundant code and rewrite code, making it more elegant.
✣ ✣ ✣
✣ ✣ ✣