banana principle

This commit is contained in:
Bob Mottram 2018-10-18 10:21:26 +01:00
parent b492a685da
commit 356aeb74ba
3 changed files with 9 additions and 2 deletions

View File

@ -19,7 +19,7 @@ Free Documentation License".
* Generated
This file last generated Wednesday, 17 October 2018 09:01AM UTC
This file last generated Thursday, 18 October 2018 09:21AM UTC
* Glossary
** (
@ -2051,6 +2051,9 @@ n. [Commodore users; perh. a deliberate phonetic mangling of boolean variable ?]
4. Used by MUDders on occasion in a more general sense related to sense 3, to refer to directing someone to another location or resource (eg. A user was asking about XYZ so I bamfed them to https://zombo.com)
*** banana principle
Also known as "perpetual beta", "git versioning" or never setting an official release date. Where you ship your software early as an alpha or beta and just keep upgrading it straight from the source repository instead of doing releases with version numbers on predefined dates. It comes from a marketing term which is an analogy to how bananas are picked while they're still unripe and shipped in that condition. An early example of this was Gmail, which remained in beta for years while also being a live production system with many users.
*** banana problem
n. [from the story of the little girl who said I know how to spell banana , but I don't know when to stop ]. Not knowing where or when to bring a production to a close (compare fencepost error ). One may say there is a banana problem of an algorithm with poorly defined or incorrect termination conditions, or in discussing the evolution of a design that may be succumbing to featuritis (see also creeping elegance , creeping featuritis ). See item 176 under HAKMEM , which describes a banana problem in a Dissociated Press implementation. Also, see one-banana problem for a superficially similar but unrelated usage.

Binary file not shown.

View File

@ -18,7 +18,7 @@ Free Documentation License".
</p>
<H2>Generated</H2>
<p>
This file last generated Wednesday, 17 October 2018 09:01AM UTC
This file last generated Thursday, 18 October 2018 09:21AM UTC
</p>
<H2>Glossary</H2>
@ -2492,6 +2492,10 @@ This file last generated Wednesday, 17 October 2018 09:01AM UTC
<p>3. In MUD circles, bamf is also used to refer to the act by which a MUD server sends a special notification to the MUD client to switch its connection to another server ( I'll set up the old site to just bamf people over to our new location. ). </p>
<p>4. Used by MUDders on occasion in a more general sense related to sense 3, to refer to directing someone to another location or resource (eg. A user was asking about XYZ so I bamfed them to https://zombo.com)</p>
<H4>banana principle</H4>
<p>
Also known as "perpetual beta", "git versioning" or never setting an official release date. Where you ship your software early as an alpha or beta and just keep upgrading it straight from the source repository instead of doing releases with version numbers on predefined dates. It comes from a marketing term which is an analogy to how bananas are picked while they're still unripe and shipped in that condition. An early example of this was Gmail, which remained in beta for years while also being a live production system with many users.
</p>
<H4>banana problem</H4>
<p>
n. [from the story of the little girl who said I know how to spell banana , but I don't know when to stop ]. Not knowing where or when to bring a production to a close (compare fencepost error ). One may say there is a banana problem of an algorithm with poorly defined or incorrect termination conditions, or in discussing the evolution of a design that may be succumbing to featuritis (see also creeping elegance , creeping featuritis ). See item 176 under HAKMEM , which describes a banana problem in a Dissociated Press implementation. Also, see one-banana problem for a superficially similar but unrelated usage.