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...) |
m |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | This strange addition to our pattern language claims to provide the holy grail of patterns. Bad code turns good using amerlioration patterns. | + | This strange addition to our pattern language claims to provide the holy grail of patterns. Bad code turns good using amerlioration patterns. [[Ward's wiki]] states that "an amelioration pattern is a prescription for how to edit (i.e., rearrange, add and delete) an existing situation (represented by a pattern) to achieve some further effect or behavior." |
| − | == How do | + | == 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 us 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]]. | ||
Amelioration patterns are a concept that appears to have originated on [[Ward's wiki]]. | Amelioration patterns are a concept that appears to have originated on [[Ward's wiki]]. | ||
| Line 11: | Line 12: | ||
== Amelioration patterns vs Refactoring == | == Amelioration patterns vs Refactoring == | ||
Is there a difference between these two concepts? | Is there a difference between these two concepts? | ||
| + | |||
| + | == Known amelioration patterns == | ||
| + | A list of know amelioration patterns: | ||
| + | * [[One Into Many]] - A proposed amelioration pattern. | ||
== See Also == | == See Also == | ||
* [[Refactoring]] | * [[Refactoring]] | ||
| + | |||
| + | [[Category: Patterns]] | ||
Latest revision as of 04:30, 5 October 2009
This strange addition to our pattern language claims to provide the holy grail of patterns. Bad code turns good using amerlioration patterns. Ward's wiki states that "an amelioration pattern is a prescription for how to edit (i.e., rearrange, add and delete) an existing situation (represented by a pattern) to achieve some further effect or behavior."
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 us 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:
- One Into Many - A proposed amelioration pattern.
