protoduction
This commit is contained in:
parent
99c26fa273
commit
135eada33e
BIN
docs/jargon.1.gz
BIN
docs/jargon.1.gz
Binary file not shown.
@ -18,7 +18,7 @@ Free Documentation License".
|
||||
</p>
|
||||
<H2>Generated</H2>
|
||||
<p>
|
||||
This file last generated Sunday, 02 December 2018 11:30AM UTC
|
||||
This file last generated Sunday, 02 December 2018 11:37AM UTC
|
||||
|
||||
</p>
|
||||
<H2>Glossary</H2>
|
||||
@ -7850,6 +7850,10 @@ This file last generated Sunday, 02 December 2018 11:30AM UTC
|
||||
<p>
|
||||
n. As used by hackers, this never refers to niceties about the proper form for addressing letters to the Papal Nuncio or the order in which one should use the forks in a Russian-style place setting; hackers don't care about such things. It is used instead to describe any set of rules that allow different machines or pieces of software to coordinate with each other without ambiguity. So, for example, it does include niceties about the proper form for addressing packets on a network or the order in which one should use the forks in the Dining Philosophers Problem. It implies that there is some common message format and an accepted set of primitives or commands that all parties involved understand, and that transactions among them follow predictable logical sequences. See also handshaking , do protocol.
|
||||
</p>
|
||||
<H4>protoduction</H4>
|
||||
<p>
|
||||
When your hacky prototype code ends up in production, often due to management pressure. "Eh, it's good enough". The term was originally used at Fermi lab.
|
||||
</p>
|
||||
<H4>provocative maintenance</H4>
|
||||
<p>
|
||||
n. [common ironic mutation of preventive maintenance ] Actions performed upon a machine at regularly scheduled intervals to ensure that the system remains in a usable state. So called because it is all too often performed by a field servoid who doesn't know what he is doing; such maintenance often induces problems, or otherwise results in the machine's remaining in an un usable state for an indeterminate amount of time. See also scratch monkey.
|
||||
|
@ -19,7 +19,7 @@ Free Documentation License".
|
||||
|
||||
* Generated
|
||||
|
||||
This file last generated Sunday, 02 December 2018 11:30AM UTC
|
||||
This file last generated Sunday, 02 December 2018 11:37AM UTC
|
||||
|
||||
* Glossary
|
||||
** (
|
||||
@ -6706,6 +6706,9 @@ n. [Mac users] See feature key.
|
||||
*** protocol
|
||||
n. As used by hackers, this never refers to niceties about the proper form for addressing letters to the Papal Nuncio or the order in which one should use the forks in a Russian-style place setting; hackers don't care about such things. It is used instead to describe any set of rules that allow different machines or pieces of software to coordinate with each other without ambiguity. So, for example, it does include niceties about the proper form for addressing packets on a network or the order in which one should use the forks in the Dining Philosophers Problem. It implies that there is some common message format and an accepted set of primitives or commands that all parties involved understand, and that transactions among them follow predictable logical sequences. See also handshaking , do protocol.
|
||||
|
||||
*** protoduction
|
||||
When your hacky prototype code ends up in production, often due to management pressure. "Eh, it's good enough". The term was originally used at Fermi lab.
|
||||
|
||||
*** provocative maintenance
|
||||
n. [common ironic mutation of preventive maintenance ] Actions performed upon a machine at regularly scheduled intervals to ensure that the system remains in a usable state. So called because it is all too often performed by a field servoid who doesn't know what he is doing; such maintenance often induces problems, or otherwise results in the machine's remaining in an un usable state for an indeterminate amount of time. See also scratch monkey.
|
||||
|
||||
|
16
entries/duck.txt
Normal file
16
entries/duck.txt
Normal file
@ -0,0 +1,16 @@
|
||||
duck
|
||||
|
||||
A software feature added simply so that management will notice it and order
|
||||
it to be removed. This gives management something to do, and makes them look
|
||||
like they are "adding value" instead of being superfluous appendages to the
|
||||
organization.
|
||||
|
||||
"The artist working on the queen animations for Battle Chess was aware of
|
||||
this tendency, and came up with an innovative solution. He did the animations
|
||||
for the queen the way that he felt would be best, with one addition: he gave
|
||||
the queen a pet duck. He animated this duck through all of the queen's
|
||||
animations, had it flapping around the corners. He also took great care to
|
||||
make sure that it never overlapped the 'actual' animation. Eventually, it came
|
||||
time for the producer to review the animation set for the queen. The producer
|
||||
sat down and watched all of the animations. When they were done, he turned to
|
||||
the artist and said, 'that looks great. Just one thing - get rid of the duck.'"
|
4
entries/hindenbug.txt
Normal file
4
entries/hindenbug.txt
Normal file
@ -0,0 +1,4 @@
|
||||
hindenbug
|
||||
|
||||
A bug with catastrophic consequences, such as deleting critical data
|
||||
or files, or causing a production line to halt.
|
5
entries/protoduction.txt
Normal file
5
entries/protoduction.txt
Normal file
@ -0,0 +1,5 @@
|
||||
protoduction
|
||||
|
||||
When your hacky prototype code ends up in production, often due to
|
||||
management pressure. "Eh, it's good enough". The term was originally
|
||||
used at Fermi lab.
|
Loading…
x
Reference in New Issue
Block a user