Difference between revisions of "Refactor code"
Jump to navigation
Jump to search
m (No Zoep) |
m (terse/full) |
||
| Line 2: | Line 2: | ||
|stage=Sparkle | |stage=Sparkle | ||
|theme=Agile, Extreme Programming, Quality | |theme=Agile, Extreme Programming, Quality | ||
|context=product development, completing {{p|product backlog item}}s | |context=product development, completing {{p|product backlog item}}s. | ||
| | |goal=sustain a minimal and elegant code base with less bugs and requiring less effort to maintain | ||
|wish=A small code base contains less bugs and is less effort to maintain. | |wish=A small code base contains less bugs and is less effort to maintain. | ||
|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. | |||
|background=Refactoring encompasses any changes to the system that leaves its behavior un- changed but enhances some nonfunctional quality (i.e. simplicity, flexibility, under- standability, or performance). | |background=Refactoring encompasses any changes to the system that leaves its behavior un- changed but enhances some nonfunctional quality (i.e. simplicity, flexibility, under- standability, or performance). | ||
|therefore=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:04, 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 un- changed but enhances some nonfunctional quality (i.e. simplicity, flexibility, under- standability, or performance).
Therefore:
Take every opportunity to eliminate redundant code and rewrite code, making it more elegant.
✣ ✣ ✣
✣ ✣ ✣