Function creep: Difference between revisions
Content deleted Content added
m Reverted edits by 72.184.208.82 (talk) to last version by Centrx |
No edit summary |
||
| Line 1: | Line 1: | ||
'''FUNCTION CREEP''', sometimes referred to as "functionality creep", is what occurs when an item, process, or procedure designed for a specific purpose ends up serving another purpose for which it was never planned to perform. |
|||
#REDIRECT [[Functionality creep]] |
|||
[http://www.functioncreep.com fuNctioN cReeP] |
|||
[[functionality creep]] |
|||
'''Terminology Debate''' |
|||
---- |
|||
"Function creep" is the preferred term rather than "functionality creep". The definitions, as given by dictionary.com, and the 37,800 hits for "function creep" on Google versus the 2,680 Google hits for "functionality creep" back up this assertation. So, in the interest of making knowledge available to eveyone, refer to the subject of this page as "function creep". Otherwise, the issue will be made muddier by trying to redefine or invent terms. |
|||
Revision as of 20:03, 4 December 2006
FUNCTION CREEP, sometimes referred to as "functionality creep", is what occurs when an item, process, or procedure designed for a specific purpose ends up serving another purpose for which it was never planned to perform.
Terminology Debate
"Function creep" is the preferred term rather than "functionality creep". The definitions, as given by dictionary.com, and the 37,800 hits for "function creep" on Google versus the 2,680 Google hits for "functionality creep" back up this assertation. So, in the interest of making knowledge available to eveyone, refer to the subject of this page as "function creep". Otherwise, the issue will be made muddier by trying to redefine or invent terms.