20 lines
3.1 KiB
HTML
20 lines
3.1 KiB
HTML
<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
|
||
<html xmlns="http://www.w3.org/1999/xhtml"><head><title>casting the runes</title><link rel="stylesheet" href="../../jargon.css" type="text/css"/><meta name="generator" content="DocBook XSL Stylesheets V1.61.0"/><link rel="home" href="../index.html" title="The Jargon File"/><link rel="up" href="../C.html" title="C"/><link rel="previous" href="casters-up-mode.html" title="casters-up mode"/><link rel="next" href="cat.html" title="cat"/></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">casting the runes</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="casters-up-mode.html">Prev</a> </td><th width="60%" align="center">C</th><td width="20%" align="right"> <a accesskey="n" href="cat.html">Next</a></td></tr></table><hr/></div><dt><a id="casting-the-runes"/><dt xmlns="" id="casting-the-runes"><b>casting the runes</b>: <span xmlns="http://www.w3.org/1999/xhtml" class="grammar">n.</span></dt></dt><dd><p> What a <a href="../G/guru.html"><i class="glossterm">guru</i></a> does when you ask him or her to
|
||
run a particular program and type at it because it never works for anyone
|
||
else; esp. used when nobody can ever see what the guru is doing different
|
||
from what J. Random Luser does. Compare
|
||
<a href="../I/incantation.html"><i class="glossterm">incantation</i></a>, <a href="../R/runes.html"><i class="glossterm">runes</i></a>,
|
||
<a href="../E/examining-the-entrails.html"><i class="glossterm">examining the entrails</i></a>; also see the AI koan about
|
||
Tom Knight in <a href="../koans.html" title="Some AI Koans">Some AI Koans</a> (in Appendix
|
||
A).</p></dd><dd><p>A correspondent from England tells us that one of ICL's most talented
|
||
systems designers used to be called out occasionally to service machines
|
||
which the <a href="../F/field-circus.html"><i class="glossterm">field circus</i></a> had given up on. Since he
|
||
knew the design inside out, he could often find faults simply by listening
|
||
to a quick outline of the symptoms. He used to play on this by going to
|
||
some site where the field circus had just spent the last two weeks solid
|
||
trying to find a fault, and spreading a diagram of the system out on a
|
||
table top. He'd then shake some chicken bones and cast them over the
|
||
diagram, peer at the bones intently for a minute, and then tell them that a
|
||
certain module needed replacing. The system would start working again
|
||
immediately upon the replacement.</p></dd><div class="navfooter"><hr/><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="casters-up-mode.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="../C.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="cat.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">casters-up mode </td><td width="20%" align="center"><a accesskey="h" href="../index.html">Home</a></td><td width="40%" align="right" valign="top"> cat</td></tr></table></div></body></html>
|