Atlas48/JargonFile
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

protoduction

Browse Source
This commit is contained in:
Bob Mottram
2018-12-02 11:37:31 +00:00
parent 99c26fa273
commit 135eada33e
6 changed files with 34 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
docs/jargon.1.gz
View File

Binary file not shown.

6
docs/jargon.html
View File

@@ -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.

5
docs/jargon.org
View File

@@ -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.