Revision as of 09:18, 8 July 2010 edit TaintedMustard (talk \| contribs) 2,893 edits No edit summary ← Previous edit		Revision as of 03:35, 5 August 2010 edit undo Robbak (talk \| contribs) 175 edits As an antipattern is a subset of a design pattern, so clarify that we are referring to legitimate patterns. Also spelling. Next edit →
Line 13: To avoid 'softcoding', consider the value to the end user of any additional flexibility you provide, and compare it with the increased complexity and related ongoing maintenance costs the added configurability involves. Several legitimate design ~~patters~~patterns exist for achieving the flexibility that softcoding attempts to provide. An application requiring more flexibility than is appropriate for a configuration file may benefit from the incorporation of a [[scripting language]]. In many cases, the appropriate design is a [[___domain specific language]] integrated in to an established scripting language. Another approach is to move most of an application's functionality in to a library, providing an API for writing related applications quickly. In [[feature design]], softcoding has other meanings.

Softcoding: Difference between revisions