Content deleted Content added
m Reverted edit by 2A00:1F:EC81:6101:2121:B99F:60F7:56DD (talk) to last version by McSly |
Added link to FizzBuzzEnterpriseEdition, a good example of misusing design patterns. |
||
Line 718:
| isbn = 9780735619678
}}
</ref> As an example, [https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpriseEdition FizzBuzzEnterpriseEdition] offers a humorous example of over-complexity introduced by design patterns. <ref name="Kragbæk2016">{{cite web
</ref>▼
| last = Kragbæk
| first = Mikael
| title = FizzBuzzEnterpriseEdition
| url = https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpriseEdition
| access-date = 2024-11-19}}
▲</ref>.
By definition, a pattern must be programmed anew into each application that uses it. Since some authors see this as a step backward from [[software reuse]] as provided by [[software componentry|components]], researchers have worked to turn patterns into components. Meyer and Arnout were able to provide full or partial componentization of two-thirds of the patterns they attempted.<ref name = "Meyer2006">{{cite journal
| |||