Amelioration patterns
From CSSEMediaWiki
(Difference between revisions)
(New page: This strange addition to our pattern language claims to provide the holy grail of patterns. Bad code turns good using amerlioration patterns. == How do Amelioration patterns fit in? == Am...) |
|||
| Line 14: | Line 14: | ||
== See Also == | == See Also == | ||
* [[Refactoring]] | * [[Refactoring]] | ||
| + | |||
| + | [[Category: Patterns]] | ||
Revision as of 15:12, 5 August 2009
This strange addition to our pattern language claims to provide the holy grail of patterns. Bad code turns good using amerlioration patterns.
How do Amelioration patterns fit in?
Amelioration patterns complete the circle of pattern types:
- Design patterns for the building blocks of code, they can be put together to create good code.
- Antipatterns show us what good code is by letting recognise bad code.
- Amelioration patterns take us from bad code to good code.
Amelioration patterns are a concept that appears to have originated on Ward's wiki.
Amelioration patterns vs Refactoring
Is there a difference between these two concepts?
