Patterns
From CSSEMediaWiki
(Difference between revisions)
| Line 12: | Line 12: | ||
My attempt at rationalising patterns can be summed up in the following (very simplistic) diagram. Do people agree? Comments??? --[[User:Matthew Harward|Matthew Harward]] 09:05, 23 July 2009 (UTC) | My attempt at rationalising patterns can be summed up in the following (very simplistic) diagram. Do people agree? Comments??? --[[User:Matthew Harward|Matthew Harward]] 09:05, 23 July 2009 (UTC) | ||
:''Oh, just to note, this is not meant to imply that one MUST use patterns to produce good code, only that considering patterns will probably produce a better end result.'' | :''Oh, just to note, this is not meant to imply that one MUST use patterns to produce good code, only that considering patterns will probably produce a better end result.'' | ||
| + | :''If you haven't heard of Amelioration Patterns before, look them up on [[Ward's wiki]]. | ||
[[Image:427 patterns.png]] | [[Image:427 patterns.png]] | ||
Revision as of 09:23, 23 July 2009
What began as design patterns has grown into a diverse movement, including antipatterns, architectural patterns, organisational patterns etc. This page is a starting point for the various families of patterns.
My attempt at rationalising patterns can be summed up in the following (very simplistic) diagram. Do people agree? Comments??? --Matthew Harward 09:05, 23 July 2009 (UTC)
- Oh, just to note, this is not meant to imply that one MUST use patterns to produce good code, only that considering patterns will probably produce a better end result.
- If you haven't heard of Amelioration Patterns before, look them up on Ward's wiki.
