| Revision as of 23:48, 22 January 2007 editBdj (talk | contribs)19,739 edits don't know how that snuck back in, see talk page.← Previous edit | Revision as of 01:09, 23 January 2007 edit undoPicaroon (talk | contribs)17,614 edits copyedits, formatting, wording changes, add quotation, rm {{Guideline list}} as being somewhat counterproductiveNext edit → | ||
| Line 1: | Line 1: | ||
| {{proposed|]}} | {{proposed|]}} | ||
| {{Guideline list}} | |||
| The fundamental fallacy of instruction creep is assuming that everybody reads instructions. | The fundamental fallacy of instruction creep is assuming that everybody reads instructions. | ||
| '''Instruction creep''' occurs when a person or persons add to a list of instructions repeatedly, causing it to increase in size and complexity over time. Instruction creep is generally frowned upon, as it causes instructions to be unmanageable and daunting. In general, people |
'''Instruction creep''' occurs when a person or persons add to a list of instructions repeatedly, causing it to increase in size and complexity over time. Instruction creep is generally frowned upon, as it causes instructions to be unmanageable and daunting. In general, people are less likely to read and follow long instructions than they are shorter ones. Although those who partake in instruction creep are probably acting in ], they may actually be acting counterproductively. Some new rules arise with the deliberate intent to control others via ] without an adequate attempt for the formation of ]. This antagonizes others even when it appears to the instigator that he's acting with proper intent. | ||
| ⚫ | Instruction creep is common in complex organizations where rules and guidelines are created by changing groups of people over extended periods of time. Note that ] supposed to be bureaucratic. | ||
| ⚫ | Instruction creep is common in complex organizations where rules and guidelines are created by changing groups of people over extended periods of time. Note that ] supposed to be bureaucratic. | ||
| == Instruction creep on Misplaced Pages == | == Instruction creep on Misplaced Pages == | ||
| ] was invented to supply ]s for process.]] | ] was invented to supply ]s for process.]] | ||
| In general, try to avoid instruction creep |
In general, try to avoid instruction creep - including that which may be perceived as instruction creep by others - here on Misplaced Pages. Procedures are popular to suggest but unpopular to follow, due to the effort to find, read, learn and abide by them. Therefore, it is more favorable to employ the ] when writing instructions on Misplaced Pages. (Note that our editors are volunteers, and are ] to follow procedure if they feel following them doesn't benefit the encyclopedia.) | ||
| Page instructions may have to be pruned at times. Feel free to remove excessive requirements ]. All new policies should be regarded as instruction creep |
Page instructions may have to be pruned at times. Feel free to remove excessive requirements ]. All new policies should be regarded as instruction creep unless it can be proved they will actually be helpful. | ||
| To quote ]: Everything should be made as simple as possible, but not simpler. | |||
| == See also == | == See also == | ||
| *] | |||
| * ] — when a computer program ends up doing more and more to the detriment of simplicity, compactness, or stability | |||
| *] | |||
| * ] — when a physical document or procedure ends up serving unexpected or unplanned purposes. | |||
| *] | *] | ||
| *] | *] | ||
| *] - on inevitable instruction creep | *] - on inevitable instruction creep | ||
| ==Source== | ==Source== | ||
| This page was inspired by the meta-wiki concept |
<center>This page was inspired by the meta-wiki concept of ].</center> | ||
Revision as of 01:09, 23 January 2007
 | The following is a proposed Misplaced Pages policy, guideline, or process. The proposal may still be in development, under discussion, or in the process of gathering consensus for adoption. | Shortcut
|
The fundamental fallacy of instruction creep is assuming that everybody reads instructions.
Instruction creep occurs when a person or persons add to a list of instructions repeatedly, causing it to increase in size and complexity over time. Instruction creep is generally frowned upon, as it causes instructions to be unmanageable and daunting. In general, people are less likely to read and follow long instructions than they are shorter ones. Although those who partake in instruction creep are probably acting in good faith, they may actually be acting counterproductively. Some new rules arise with the deliberate intent to control others via fiat without an adequate attempt for the formation of consensus. This antagonizes others even when it appears to the instigator that he's acting with proper intent.
Instruction creep is common in complex organizations where rules and guidelines are created by changing groups of people over extended periods of time. Note that Misplaced Pages is not supposed to be bureaucratic.
Instruction creep on Misplaced Pages
In general, try to avoid instruction creep - including that which may be perceived as instruction creep by others - here on Misplaced Pages. Procedures are popular to suggest but unpopular to follow, due to the effort to find, read, learn and abide by them. Therefore, it is more favorable to employ the KISS principle when writing instructions on Misplaced Pages. (Note that our editors are volunteers, and are not obliged to follow procedure if they feel following them doesn't benefit the encyclopedia.)
Page instructions may have to be pruned at times. Feel free to remove excessive requirements as you see fit. All new policies should be regarded as instruction creep unless it can be proved they will actually be helpful.
To quote Albert Einstein: Everything should be made as simple as possible, but not simpler.
See also
- Creeping featurism
- Functionality creep
- Red tape
- Bureaucracy
- Iron law of oligarchy - on inevitable instruction creep