Amelioration patterns
From CSSEMediaWiki
(Difference between revisions)
(→How do amelioration patterns fit in?) |
|||
| Line 3: | Line 3: | ||
== How do amelioration patterns fit in? == | == How do amelioration patterns fit in? == | ||
Amelioration patterns complete the circle of pattern types: | 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. | + | * [[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. | + | * [[Antipatterns]] show us what good code is by letting recognise bad code. |
* Amelioration patterns take us from bad code to good code. | * Amelioration patterns take us from bad code to good code. | ||
* According to [[Ward's wiki]], these patterns do the direct opposite of [[Antipatterns]]. | * According to [[Ward's wiki]], these patterns do the direct opposite of [[Antipatterns]]. | ||
Revision as of 15:23, 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.
Contents |
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.
- According to Ward's wiki, these patterns do the direct opposite of Antipatterns.
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?
Known amelioration patterns
A list of know amelioration patterns:
