view release on metacpan or  search on metacpan

factpacks/jargon.fact  view on Meta::CPAN

bignum => /big'nuhm/ [orig. from MIT MacLISP] n. 1. [techspeak] A multiple-precision computer representation for very large integers. More generally, any very large number. "Have you ever looked at the United States Budget? There's bignums for you!" ...
bigot => n. A person who is religiously attached to a particular computer, language, operating system, editor, or other tool (see {religious issues}). Usually found with a specifier; thus, `cray bigot', {ITS bigot}, `APL bigot', `VMS bigot', {Berkele...
bit => [from the mainstream meaning and `Binary digIT'] n. 1. [techspeak] The unit of information; the amount of information obtained by asking a yes-or-no question for which the two outcomes are equally probable. 2. [techspeak] A computational quant...
bit bang => n. Transmission of data on a serial line, when accomplished by rapidly tweaking a single output bit at the appropriate times. The technique is a simple loop with eight OUT and SHIFT instruction pairs for each byte. Input is more interesti...
bit bang2 => and output at the same time) is one way to separate the real hackers from the wannabees. Bit bang was used on certain early models of Prime computers, presumably when UARTs were too expensive, and on archaic Z80 micros with a Zilog PIO b...
bit bang3 => instance of the {cycle of reincarnation}, this technique is now (1991) coming back into use on some RISC architectures because it consumes such an infinitesimal part of the processor that it actually makes sense not to have a UART. 
bit bashing => n. (alt. `bit diddling' or {bit twiddling}) Term used to describe any of several kinds of low-level programming characterized by manipulation of bit, flag, nybble, and other smaller-than-character-sized pieces of data; these include lo...
bit bashing2 => encryption algorithms, checksum and error-correcting codes, hash functions, some flavors of graphics programming (see bitblt), and assembler/compiler code generation. May connote either tedium or a real technical challenge (more usual...
bit bashing3 => decoding for the new tape driver looks pretty solid but the bit-bashing for the control registers still has bugs." See also {bit bang}, {mode bit}. 
bit bucket => n. 1. The universal data sink (originally, the mythical receptacle used to catch bits when they fall off the end of a register during a shift instruction). Discarded, lost, or destroyed data is said to have `gone to the bit bucket'. On ...
bit bucket2 => /dev/null. Sometimes amplified as `the Great Bit Bucket in the Sky'. 2. The place where all lost mail and news messages eventually go. The selection is performed according to {Finagle's Law}; important mail is much more likely to end u...
bit bucket3 => mail, which has an almost 100% probability of getting delivered. Routing to the bit bucket is automatically performed by mail-transfer agents, news systems, and the lower layers of the network. 3. The ideal location for all unwanted ma...
bit bucket4 => article to the bit bucket." Such a request is guaranteed to overflow one's mailbox with flames. 4. Excuse for all mail that has not been sent. "I mailed you those figures last week; they must have ended in the bit bucket." Compare {bla...
bit bucket5 => in jest. It is based on the fanciful notion that bits are objects that are not destroyed but only misplaced. This appears to have been a mutation of an earlier term `bit box', about which the same legend was current; old-time hackers a...
bit bucket6 => told that when the CPU stored bits into memory it was actually pulling them `out of the bit box'. See also {chad box}. Another variant of this legend has it that, as a consequence of the `parity preservation law', the number of 1 bits ...
bit bucket7 => equal the number of 0 bits. Any imbalance results in bits filling up the bit bucket. A qualified computer technician can empty a full bit bucket as part of scheduled maintenance. 
bit decay => n. See {bit rot}. People with a physics background tend to prefer this one for the analogy with particle decay. See also computron, {quantum bogodynamics}.
bit rot => n. Also {bit decay}. Hypothetical disease the existence of which has been deduced from the observation that unused programs or features will often stop working after sufficient time has passed, even if `nothing has changed'. The theory exp...
bit rot2 => were radioactive. As time passes, the contents of a file or the code in a program will become increasingly garbled. There actually are physical processes that produce such effects (alpha particles generated by trace radionuclides in ceram...
bit rot3 => change the contents of a computer memory unpredictably, and various kinds of subtle media failures can corrupt files in mass storage), but they are quite rare (and computers are built with error-detecting circuitry to compensate for them)...
bit rot4 => hackers that cosmic rays are among the causes of such events turns out to be a myth; see the {cosmic rays} entry for details. The term {software rot} is almost synonymous. Software rot is the effect, bit rot the notional cause. 
bit twiddling => n. 1. (pejorative) An exercise in tuning in which incredible amounts of time and effort go to produce little noticeable improvement, often with the result that the code has become incomprehensible. 2. Aimless small modification to a ...
bit twiddling2 => goal. 3. Approx. syn. for {bit bashing}; esp. used for the act of frobbing the device control register of a peripheral in an attempt to get it back to a known state. 
bit-paired keyboard => n. obs. (alt. `bit-shift keyboard') A non-standard keyboard layout that seems to have originated with the Teletype ASR-33 and remained common for several years on early computer equipment. The ASR-33 was a mechanical device (se...
bit-paired keyboard2 => generate the character codes from keystrokes was by some physical linkage. The design of the ASR-33 assigned each character key a basic pattern that could be modified by flipping bits if the SHIFT or the CTRL key was pressed. ...
bit-paired keyboard3 => more of a Rube Goldberg kluge than it already was, the design had to group characters that shared the same basic bit pattern on one key. This is why the characters !"#$%&'() appear where they do on a Teletype (thankfully, they...
bit-paired keyboard4 => was *not* the weirdest variant of the QWERTY layout widely seen, by the way; that prize should probably go to one of several (differing) arrangements on IBM's even clunkier 026 and 029 card punches. When electronic terminals b...
bit-paired keyboard5 => there was no agreement in the industry over how the keyboards should be laid out. Some vendors opted to emulate the Teletype keyboard, while others used the flexibility of electronic circuitry to make their product look like a...
bit-paired keyboard6 => alternatives became known as `bit-paired' and `typewriter-paired' keyboards. To a hacker, the bit-paired keyboard seemed far more logical --- and because most hackers in those days had never learned to touch-type, there was li...
bit-paired keyboard7 => users to adapt keyboards to the typewriter standard. The doom of the bit-paired keyboard was the large-scale introduction of the computer terminal into the normal office environment, where out-and-out technophobes were expecte...
bit-paired keyboard8 => `typewriter-paired' standard became universal, `bit-paired' hardware was quickly junked or relegated to dusty corners, and both terms passed into disuse. 
bitblt => /bit'blit/ n. [from BLT, q.v.] 1. Any of a family of closely related algorithms for moving and copying rectangles of bits between main and display memory on a bit-mapped device, or between two areas of either main or display memory (the req...
BITNET => /bit'net/ [acronym Because It's Time NETwork] n. Everybody's least favorite piece of the network (see {network, the}). The BITNET hosts are a collection of IBM dinosaurs and VAXen (the latter with lobotomized comm hardware) that communicate...
bits => n.pl. 1. Information. Examples "I need some bits about file formats." ("I need to know about file formats.") Compare {core dump}, sense 4. 2. Machine-readable representation of a document, specifically as contrasted with paper "I have only a ...
bitty box => /bit'ee boks/ n. 1. A computer sufficiently small, primitive, or incapable as to cause a hacker acute claustrophobia at the thought of developing software for it. Especially used of small, obsolescent, single-tasking-only personal machin...
bitty box2 => Sinclair, VIC-20, TRS-80, or IBM PC. 2. [Pejorative] More generally, the opposite of `real computer' (see {Get a real computer!}). See also mess-dos, toaster, and toy. 
bixie => /bik'see/ n. Variant emoticons used on BIX (the Byte Information eXchange). The smiley bixie is <@_@>, apparently intending to represent two cartoon eyes and a mouth. A few others have been reported.
black art => n. A collection of arcane, unpublished, and (by implication) mostly ad-hoc techniques developed for a particular application or systems area (compare {black magic}). VLSI design and compiler code optimization were (in their beginnings) c...
black art2 => art; as theory developed they became {deep magic}, and once standard textbooks had been written, became merely {heavy wizardry}. The huge proliferation of formal and informal channels for spreading around new computer-related technologi...
black art3 => made both the term `black art' and what it describes less common than formerly. See also {voodoo programming}. 
black hole => n. When a piece of email or netnews disappears mysteriously between its origin and destination sites (that is, without returning a {bounce message}) it is commonly said to have `fallen into a black hole'. "I think there's a black hole a...
black hole2 => site foovax has been dropping a lot of stuff on the floor lately (see {drop on the floor}). The implied metaphor of email as interstellar travel is interesting in itself. Compare {bit bucket}. 
black magic => n. A technique that works, though nobody really understands why. More obscure than {voodoo programming}, which may be done by cookbook. Compare also {black art}, {deep magic}, and {magic number} (sense 2).
blast => 1. vt.,n. Synonym for BLT, used esp. for large data sends over a network or comm line. Opposite of snarf. Usage uncommon. The variant `blat' has been reported. 2. vt. [HP/Apollo] Synonymous with nuke (sense 3). Sometimes the message `Unable ...
blat => n. 1. Syn. blast, sense 1. 2. See thud.
bletch => /blech/ [from Yiddish/German `brechen', to vomit, poss. via comic-strip exclamation `blech'] interj. Term of disgust. Often used in "Ugh, bletch". Compare barf.
bletcherous => /blech'*-r*s/ adj. Disgusting in design or function; esthetically unappealing. This word is seldom used of people. "This keyboard is bletcherous!" (Perhaps the keys don't work very well, or are misplaced.) See losing, cretinous, bagbit...
blinkenlights => /blink'*n-litz/ n. Front-panel diagnostic lights on a computer, esp. a dinosaur. Derives from the last word of the famous blackletter-Gothic sign in mangled pseudo-German that once graced about half the computer rooms in the English-...
blit => /blit/ vt. 1. To copy a large array of bits from one part of a computer's memory to another part, particularly when the memory is being used to determine what is shown on a display screen. "The storage allocator picks through the table and co...
blitter => /blit'r/ n. A special-purpose chip or hardware system built to perform blit operations, esp. used for fast implementation of bit-mapped graphics. The Commodore Amiga and a few other micros have these, but in 1991 the trend is away from the...
blivet => /bliv'*t/ [allegedly from a World War II military term meaning "ten pounds of manure in a five-pound bag"] n. 1. An intractable problem. 2. A crucial piece of hardware that can't be fixed or replaced if it breaks. 3. A tool that has been ha...
block => [from process scheduling terminology in OS theory] 1. vi. To delay or sit idle while waiting for something. "We're blocking until everyone gets here." Compare busy-wait. 2. `block on' vt. To block, waiting for (something). "Lunch is blocked ...
block transfer computations => n. From the television series "Dr. Who", in which it referred to computations so fiendishly subtle and complex that they could not be performed by machines. Used to refer to any task that should be expressible as an alg...
blow an EPROM => /bloh *n ee'prom/ v. (alt. `blast an EPROM', `burn an EPROM') To program a read-only memory, e.g. for use with an embedded system. This term arises because the programming process for the Programmable Read-Only Memories (PROMs) that ...
blow an EPROM2 => Programmable Read-Only Memories (EPROMs) involved intentionally blowing tiny electrical fuses on the chip. Thus, one was said to `blow' (or `blast') a PROM, and the terminology carried over even though the write process on EPROMs is...
blow away => vt. To remove (files and directories) from permanent storage, generally by accident. "He reformatted the wrong partition and blew away last night's netnews." Oppose nuke.
blow out => vi. Of software, to fail spectacularly; almost as serious as {crash and burn}. See {blow past}, {blow up}.
blow past => vt. To {blow out} despite a safeguard. "The server blew past the 5K reserve buffer."
blow up => vi. 1. [scientific computation] To become unstable. Suggests that the computation is diverging so rapidly that it will soon overflow or at least go nonlinear. 2. Syn. {blow out}.
BLT => /B-L-T/, /bl*t/ or (rarely) /belt/ n.,vt. Synonym for blit. This is the original form of blit and the ancestor of bitblt. It referred to any large bit-field copy or move operation (one resource-intensive memory-shuffling operation done on pre-...
Blue Book => n. 1. Informal name for one of the three standard references on the page-layout and graphics-control language PostScript (`PostScript Language Tutorial and Cookbook', Adobe Systems, Addison-Wesley 1985, QA76.73.P67P68, ISBN 0-201-10179-3...
Blue Book2 => known as the {Green Book} and {Red Book}. 2. Informal name for one of the three standard references on Smalltalk `Smalltalk-80 The Language and its Implementation', David Robson, Addison-Wesley 1983, QA76.8.S635G64, ISBN 0-201-11371-63 ...
Blue Book3 => and red books). 3. Any of the 1988 standards issued by the CCITT's ninth plenary assembly. Until now, they have changed color each review cycle (1984 was {Red Book}, 1992 would be {Green Book}); however, it is rumored that this conventi...
Blue Book4 => 1992. These include, among other things, the X.400 email spec and the Group 1 through 4 fax standards. See also {{book titles}}. 
Blue Glue => [IBM] n. IBM's SNA (Systems Network Architecture), an incredibly losing and bletcherous communications protocol widely favored at commercial shops that don't know any better. The official IBM definition is "that which binds blue boxes to...
Blue Glue2 => loathing}. It may not be irrelevant that {Blue Glue} is the trade name of a 3M product that is commonly used to hold down the carpet squares to the removable panel floors common in {dinosaur pens}. A correspondent at U. Minn. reports th...
Blue Glue3 => 80 bottles of the stuff hanging about, so they often refer to any messy work to be done as `using the blue glue'. 
blue goo => n. Term for `police' nanobots intended to prevent {gray goo}, denature hazardous waste, destroy pollution, put ozone back into the stratosphere, prevent halitosis, and promote truth, justice, and the American way, etc. See {nanotechnology...
BNF => /B-N-F/ n. 1. [techspeak] Acronym for `Backus-Naur Form', a metasyntactic notation used to specify the syntax of programming languages, command sets, and the like. Widely used for language descriptions but seldom documented anywhere, so that i...
boa => [IBM] n. Any one of the fat cables that lurk under the floor in a {dinosaur pen}. Possibly so called because they display a ferocious life of their own when you try to lay them straight and flat after they have been coiled for some time. It is...
board => n. 1. In-context synonym for bboard; sometimes used even for USENET newsgroups. 2. An electronic circuit board (compare card).
boat anchor => n. 1. Like doorstop but more severe; implies that the offending hardware is irreversibly dead or useless. "That was a working motherboard once. One lightning strike later, instant boat anchor!" 2. A person who just takes up space.
bogo-sort => /boh`goh-sort'/ n. (var. `stupid-sort') The archetypical perversely awful algorithm (as opposed to {bubble sort}, which is merely the generic *bad* algorithm). Bogo-sort is equivalent to repeatedly throwing a deck of cards in the air, pi...
bogometer => /boh-gom'-*t-er/ n. See bogosity. Compare the `wankometer' described in the wank entry; see also bogus.
bogon => /boh'gon/ [by analogy with proton/electron/neutron, but doubtless reinforced after 1980 by the similarity to Douglas Adams's `Vogons'; see the Bibliography] n. 1. The elementary particle of bogosity (see {quantum bogodynamics}). For instance...
bogon filter => /boh'gon fil'tr/ n. Any device, software or hardware, that limits or suppresses the flow and/or emission of bogons. "Engineering hacked a bogon filter between the Cray and the VAXen, and now we're getting fewer dropped packets." See a...
bogon flux => /boh'gon fluhks/ n. A measure of a supposed field of bogosity emitted by a speaker, measured by a bogometer; as a speaker starts to wander into increasing bogosity a listener might say "Warning, warning, bogon flux is rising". See {quan...
bogosity => /boh-go's*-tee/ n. 1. The degree to which something is bogus. At CMU, bogosity is measured with a bogometer; in a seminar, when a speaker says something bogus, a listener might raise his hand and say "My bogometer just triggered". More ex...
bogotify => /boh-go't*-fi/ vt. To make or become bogus. A program that has been changed so many times as to become completely disorganized has become bogotified. If you tighten a nut too hard and strip the threads on the bolt, the bolt has become bog...
bogue out => /bohg owt/ vi. To become bogus, suddenly and unexpectedly. "His talk was relatively sane until somebody asked him a trick question; then he bogued out and did nothing but flame afterwards." See also bogosity, bogus.
bogus => adj. 1. Non-functional. "Your patches are bogus." 2. Useless. "OPCON is a bogus program." 3. False. "Your arguments are bogus." 4. Incorrect. "That algorithm is bogus." 5. Unbelievable. "You claim to have solved the halting problem for Turin...
Bohr bug => /bohr buhg/ [from quantum physics] n. A repeatable bug; one that manifests reliably under a possibly unknown but well-defined set of conditions. Antonym of heisenbug; see also mandelbug.
boink => /boynk/ [USENET ascribed there to the TV series "Cheers" and "Moonlighting"] 1. To have sex with; compare bounce, sense 3. (This is mainstream slang.) In Commonwealth hackish the variant `bonk' is more common. 2. After the original Peter Kor...
bomb => 1. v. General synonym for crash (sense 1) except that it is not used as a noun; esp. used of software or OS failures. "Don't run Empire with less than 32K stack, it'll bomb." 2. n.,v. Atari ST and Macintosh equivalents of a UNIX `panic' or Am...
bondage-and-discipline language => A language (such as Pascal, Ada, APL, or Prolog) that, though ostensibly general-purpose, is designed so as to enforce an author's theory of `right programming' even though said theory is demonstrably inadequate for...
bondage-and-discipline language2 => general-purpose programming. Often abbreviated `B&D'; thus, one may speak of things "having the B&D nature". See {Pascal}; oppose {languages of choice}. 
bonk/oif => /bonk/, /oyf/ interj. In the MUD community, it has become traditional to express pique or censure by `bonking' the offending person. There is a convention that one should acknowledge a bonk by saying `oif!' and a myth to the effect that f...
book titles => There is a tradition in hackerdom of informally tagging important textbooks and standards documents with the dominant color of their covers or with some other conspicuous feature of the cover. Many of these are described in this lexico...
book titles2 => {Aluminum Book}, {Blue Book}, {Cinderella Book}, {Devil Book}, {Dragon Book}, {Green Book}, {Orange Book}, {Pink-Shirt Book}, {Purple Book}, {Red Book}, {Silver Book}, {White Book}, {Wizard Book}, {Yellow Book}, and bible.boot [techsp...
book titles3 => v.,n. To load and initialize the operating system on a machine. This usage is no longer jargon (having passed into techspeak) but has given rise to some derivatives that are still jargon. The derivative `reboot' implies that the machi...
book titles4 => that the boot is a bounce intended to clear some state of wedgitude. This is sometimes used of human thought processes, as in the following exchange "You've lost me." "OK, reboot. Here's the theory...." This term is also found in the ...
book titles5 => power-off condition) and `warm boot' (with the CPU and all devices already powered up, as after a hardware reset or software crash). Another variant `soft boot', reinitialization of only part of a system, under control of other softwa...
book titles6 => the mess-dos emulator, control-alt-insert will cause a soft-boot of the emulator, while leaving the rest of the system running." Opposed to this there is `hard boot', which connotes hostility towards or frustration with the machine be...
book titles7 => hard-boot this losing Sun." "I recommend booting it hard." Historical note this term derives from `bootstrap loader', a short program that was read in from cards or paper tape, or toggled in from the front panel switches. This program...
book titles8 => were expended on making it short in order to minimize the labor and chance of error involved in toggling it in), but was just smart enough to read in a slightly more complex program (usually from a card or paper tape reader), to which...
book titles9 => turn was smart enough to read the application or operating system from a magnetic tape drive or disk drive. Thus, in successive steps, the computer `pulled itself up by its bootstraps' to a useful operating state. Nowadays the bootstr...
book titles10 => and reads the first stage in from a fixed location on the disk, called the `boot block'. When this program gains control, it is powerful enough to load the actual OS and hand control over to it. 
bottom-up implementation => n. Hackish opposite of the techspeak term `top-down design'. It is now received wisdom in most programming cultures that it is best to design from higher levels of abstraction down to lower, specifying sequences of action ...
bottom-up implementation2 => to actual code. Hackers often find (especially in exploratory designs that cannot be closely specified in advance) that it works best to *build* things in the opposite order, by writing and testing a clean set of primitiv...
bounce => v. 1. [perhaps from the image of a thrown ball bouncing off a wall] An electronic mail message that is undeliverable and returns an error notification to the sender is said to `bounce'. See also {bounce message}. 2. [Stanford] To play volle...
bounce message => [UNIX] n. Notification message returned to sender by a site unable to relay email to the intended {{Internet address}} recipient or the next link in a {bang path} (see bounce). Reasons might include a nonexistent or misspelled usern...
bounce message2 => Bounce messages can themselves fail, with occasionally ugly results; see {sorcerer's apprentice mode}. The term `bounce mail' is also common. 
box => n. 1. A computer; esp. in the construction `foo box' where foo is some functional qualifier, like `graphics', or the name of an OS (thus, `UNIX box', `MS-DOS box', etc.) "We preprocess the data on UNIX boxes before handing it up to the mainfra...
boxed comments => n. Comments (explanatory notes attached to program instructions) that occupy several lines by themselves; so called because in assembler and C code they are often surrounded by a box in a style something like this Common variants of...
boxed comments2 => column 2 or add a matching row of asterisks closing the right side of the box. The sparest variant omits all but the comment delimiters themselves; the `box' is implied. Oppose {winged comments}. 
boxen => /bok'sn/ [by analogy with VAXen] pl.n. Fanciful plural of box often encountered in the phrase `UNIX boxen', used to describe commodity {UNIX} hardware. The connotation is that any two UNIX boxen are interchangeable.
boxology => /bok-sol'*-jee/ n. Syn. {ASCII art}. This term implies a more restricted domain, that of box-and-arrow drawings. "His report has a lot of boxology in it." Compare macrology.
bozotic => /boh-zoh'tik/ or /boh-zo'tik/ [from the name of a TV clown even more losing than Ronald McDonald] adj. Resembling or having the quality of a bozo; that is, clownish, ludicrously wrong, unintentionally humorous. Compare wonky, demented. Not...
BQS => /B-Q-S/ adj. Syn. {Berkeley Quality Software}.
brain dump => n. The act of telling someone everything one knows about a particular topic or project. Typically used when someone is going to let a new party maintain a piece of code. Conceptually analogous to an operating system {core dump} in that ...
brain dump2 => before an exit. "You'll have to give me a brain dump on FOOBAR before you start your new job at HackerCorp." See {core dump} (sense 4). At Sun, this is also known as `TOI' (transfer of information). 
brain-damaged => 1. [generalization of `Honeywell Brain Damage' (HBD), a theoretical disease invented to explain certain utter cretinisms in Honeywell {Multics}] adj. Obviously wrong; cretinous; demented. There is an implication that the person respo...
brain-dead => adj. Brain-damaged in the extreme. It tends to imply terminal design failure rather than malfunction or simple stupidity. "This comm program doesn't know how to send a break --- how brain-dead!"
braino => /bray'no/ n. Syn. for thinko.
branch to Fishkill => [IBM from the location of one of the corporation's facilities] n. Any unexpected jump in a program that produces catastrophic or just plain weird results. See {jump off into never-never land}, hyperspace.
brand brand brand => n. Humorous catch-phrase from BartleMUDs, in which players were described carrying a list of objects, the most common of which would usually be a brand. Often used as a joke in {talk mode} as in "Fred the wizard is here, carrying...
brand brand brand2 => kettle broadsword flamethrower". A brand is a torch, of course; one burns up a lot of those exploring dungeons. Prob. influenced by the famous Monty Python "Spam" skit. 
break => 1. vt. To cause to be broken (in any sense). "Your latest patch to the editor broke the paragraph commands." 2. v. (of a program) To stop temporarily, so that it may debugged. The place where it stops is a `breakpoint'. 3. [techspeak] vi. To...
breath-of-life packet => [XEROX PARC] n. An Ethernet packet that contained bootstrap (see boot) code, periodically sent out from a working computer to infuse the `breath of life' into any computer on the network that had happened to crash. The machin...
breath-of-life packet2 => would wait for such a packet after a catastrophic error. 
breedle => n. See feep.

factpacks/jargon.fact  view on Meta::CPAN

code police2 => violation is dangerous, or ironically, to suggest that the practice under discussion is condemned mainly by anal-retentive weenies. "Dike out that goto or the code police will get you!" The ironic usage is perhaps more common. 
codewalker => n. A program component that traverses other programs for a living. Compilers have codewalkers in their front ends; so do cross-reference generators and some database front ends. Other utility programs that try to do too much with source...
coefficient of X => n. Hackish speech makes rather heavy use of pseudo-mathematical metaphors. Four particularly important ones involve the terms `coefficient', `factor', `index', and `quotient'. They are often loosely applied to things you cannot re...
coefficient of X2 => there are subtle distinctions among them that convey information about the way the speaker mentally models whatever he or she is describing. `Foo factor' and `foo quotient' tend to describe something for which the issue is one of...
coefficient of X3 => example is {fudge factor}. It's not important how much you're fudging; the term simply acknowledges that some fudging is needed. You might talk of liking a movie for its silliness factor. Quotient tends to imply that the property...
coefficient of X4 => "I would have won except for my luck quotient." This could also be "I would have won except for the luck factor", but using *quotient* emphasizes that it was bad luck overpowering good luck (or someone else's good luck overpoweri...
coefficient of X5 => `coefficient of foo' both tend to imply that foo is, if not strictly measurable, at least something that can be larger or smaller. Thus, you might refer to a paper or person as having a `high bogosity index', whereas you would be...
coefficient of X6 => bogosity factor'. `Foo index' suggests that foo is a condensation of many quantities, as in the mundane cost-of-living index; `coefficient of foo' suggests that foo is a fundamental quantity, as in a coefficient of friction. The ...
coefficient of X7 => one of personal preference; e.g., some people might feel that bogosity is a fundamental attribute and thus say `coefficient of bogosity', whereas others might feel it is a combination of factors and thus say `bogosity index'. 
cokebottle => /kohk'bot-l/ n. Any very unusual character, particularly one you can't type because it it isn't on your keyboard. MIT people used to complain about the `control-meta-cokebottle' commands at SAIL, and SAIL people complained right back ab...
cold boot => n. See boot.
COME FROM => n. A semi-mythical language construct dual to the `go to'; `COME FROM' <label> would cause the referenced label to act as a sort of trapdoor, so that if the program ever reached it control would quietly and automagically be transferred t...
COME FROM2 => FROM'. `COME FROM' was first proposed in a Datamation article of December 1973 (reprinted in the April 1984 issue of `Communications of the ACM') that parodied the then-raging `structured programming' {holy wars} (see {considered harmfu...
COME FROM3 => the `assigned COME FROM' and the `computed COME FROM' (parodying some nasty control constructs in FORTRAN and some extended BASICs). Of course, multi-tasking (or non-determinism) could be implemented by having more than one `COME FROM' ...
COME FROM4 => label. In some ways the FORTRAN `DO' looks like a `COME FROM' statement. After the terminating statement number/`CONTINUE' is reached, control continues at the statement following the DO. Some generous FORTRANs would allow arbitrary sta...
COME FROM5 => the statement, leading to examples like DO 10 I=1,LIMIT C imagine many lines of code here, leaving the C original DO statement lost in the spaghetti... WRITE(6,10) I,FROB(I) 10 FORMAT(1X,I5,G10.4) in which the trapdoor is just after the...
COME FROM6 => statement labeled 10. (This is particularly surprising because the label doesn't appear to have anything to do with the flow of control at all!) While sufficiently astonishing to the unsuspecting reader, this form of `COME FROM' stateme...
COME FROM7 => all, control will eventually pass to the following statement. The implementation of the general form was left to Univac FORTRAN, ca. 1975. The statement `AT 100' would perform a `COME FROM 100'. It was intended strictly as a debugging a...
COME FROM8 => promised to anyone so deranged as to use it in production code. More horrible things had already been perpetrated in production languages, however; doubters need only contemplate the `ALTER' verb in COBOL. `COME FROM' was supported unde...
COME FROM9 => 15 years later, in C-INTERCAL (see INTERCAL, retrocomputing); knowledgeable observers are still reeling from the shock. 
comm mode => /kom mohd/ [ITS from the feature supporting on-line chat; the term may spelled with one or two m's] Syn. for {talk mode}.
command key => [Mac users] n. The Macintosh key with the cloverleaf graphic on its keytop; sometimes referred to as `flower', `pretzel', `clover', `propeller', `beanie' (an apparent reference to the major feature of a propeller beanie), or splat. The...
command key2 => The proliferation of terms for this creature may illustrate one subtle peril of iconic interfaces. 
comment out => vt. To surround a section of code with comment delimiters or to prefix every line in the section with a comment marker; this prevents it from being compiled or interpreted. Often done when the code is redundant or obsolete, but you wan...
comment out2 => the intent of the active code clearer; also when the code in that section is broken and you want to bypass it in order to debug some other part of the code. Compare {condition out}, usually the preferred technique in languages (such a...
Commonwealth Hackish => n. Hacker jargon as spoken outside the U.S., esp. in the British Commonwealth. It is reported that Commonwealth speakers are more likely to pronounce truncations like `char' and `soc', etc., as spelled (/char/, /sok/), as oppo...
Commonwealth Hackish2 => Dots in newsgroup names tend to be pronounced more often (so soc.wibble is /sok dot wib'l/ rather than /sohsh wib'l/). The prefix meta may be pronounced /mee't*/; similarly, Greek letter beta is often /bee't*/, zeta is often ...
Commonwealth Hackish3 => Preferred metasyntactic variables include `eek', `ook', `frodo', and `bilbo'; `wibble', `wobble', and in emergencies `wubble'; `banana', `wombat', `frog', fish, and so on and on (see foo, sense 4). Alternatives to verb doubli...
Commonwealth Hackish4 => `frenzy' (as in feeding frenzy), and `city' (examples "barf city!" "hack-o-rama!" "core dump frenzy!"). Finally, note that the American terms `parens', `brackets', and `braces' for (), [], and {} are uncommon; Commonwealth ha...
Commonwealth Hackish5 => brackets', and `curly brackets'. Also, the use of `pling' for bang is common outside the United States. See also attoparsec, calculator, chemist, {console jockey}, fish, {go-faster stripes}, grunge, hakspek, {heavy metal}, {l...
Commonwealth Hackish6 => fixer}, noddy, psychedelicware, plingnet, {raster blaster}, seggie, {terminal junkie}, {tick-list features}, weeble, weasel, YABA, and notes or definitions under {Bad Thing}, barf, bogus, bum, {chase pointers}, {cosmic rays},...
Commonwealth Hackish7 => crunch, dodgy, gonk, hamster, hardwarily, mess-dos, nybble, proglet, root, SEX, tweak, and xyzzy. 
compact => adj. Of a design, describes the valuable property that it can all be apprehended at once in one's head. This generally means the thing created from the design can be used with greater facility and fewer errors than an equivalent tool that ...
compiler jock => n. See jock (sense 2).
compress => [UNIX] vt. When used without a qualifier, generally refers to crunching of a file using a particular C implementation of Lempel-Ziv compression by James A. Woods et al. and widely circulated via USENET. Use of crunch itself in this sense ...
Compu$erve => n. See CI$.
computer confetti => n. Syn. chad. Though this term is common, this use of the punched-card chad is not a good idea, as the pieces are stiff and have sharp corners that could injure the eyes. GLS reports that he once attended a wedding at MIT during ...
computer confetti2 => enthusiastically threw chad instead of rice. The groom later grumbled that he and his bride had spent most of the evening trying to get the stuff out of their hair. 
computer geek => n. One who eats (computer) bugs for a living. One who fulfills all the dreariest negative stereotypes about hackers an asocial, malodorous, pasty-faced monomaniac with all the personality of a cheese grater. Cannot be used by outside...
computer geek2 => hackers; compare black-on-black usage of `nigger'. A computer geek may be either a fundamentally clueless individual or a proto-hacker in {larval stage}. Also called `turbo nerd', `turbo geek'. See also clustergeeking, {geek out}, w...
computron => /kom'pyoo-tron`/ n. 1. A notional unit of computing power combining instruction speed and storage capacity, dimensioned roughly in instructions-per-second times megabytes-of-main-store times megabytes-of-mass-storage. "That machine can't...
condition out => vt. To prevent a section of code from being compiled by surrounding it with a conditional-compilation directive whose condition is always false. The canonical examples are `#if 0' (or `#ifdef notdef', though some find this bletcherou...
condom => n. 1. The protective plastic bag that accompanies 3.5-inch microfloppy diskettes. Rarely, also used of (paper) disk envelopes. Unlike the write protect tab, the condom (when left on) not only impedes the practice of SEX but has also been sh...
connector conspiracy => [probably came into prominence with the appearance of the KL-10 (one model of the PDP-10), none of whose connectors matched anything else] n. The tendency of manufacturers (or, by extension, programmers or purveyors of anythin...
connector conspiracy2 => that don't fit together with the old stuff, thereby making you buy either all new stuff or expensive interface devices. The KL-10 Massbus connector was actually *patented* by DEC, which reputedly refused to license the design...
connector conspiracy3 => parties out of competition for the lucrative Massbus peripherals market. This is a source of never-ending frustration for the diehards who maintain older PDP-10 or VAX systems. Their CPUs work fine, but they are stuck with dy...
connector conspiracy4 => drives with low capacity and high power requirements. In these latter days of open-systems computing this term has fallen somewhat into disuse, to be replaced by the observation that "Standards are great! There are so *many* ...
cons => /konz/ or /kons/ [from LISP] 1. vt. To add a new element to a specified list, esp. at the top. "OK, cons picking a replacement for the console TTY onto the agenda." 2. `cons up' vt. To synthesize from smaller pieces "to cons up an example". I...
considered harmful => adj. Edsger W. Dijkstra's note in the March 1968 `Communications of the ACM', "Goto Statement Considered Harmful", fired the first salvo in the structured programming wars. Amusingly, the ACM considered the resulting acrimony su...
considered harmful2 => policy) no longer print an article taking so assertive a position against a coding practice. In the ensuing decades, a large number of both serious papers and parodies have borne titles of the form "X considered Y". The structu...
considered harmful3 => over with the realization that both sides were wrong, but use of such titles has remained as a persistent minor in-joke (the `considered silly' found at various places in this lexicon is related). 
console => n. 1. The operator's station of a mainframe. In times past, this was a privileged location that conveyed godlike powers to anyone with fingers on its keys. Under UNIX and other modern timesharing OSes, such privileges are guarded by passwo...
console jockey => n. See {terminal junkie}.
content-free => [by analogy with techspeak `context-free'] adj. Used of a message that adds nothing to the recipient's knowledge. Though this adjective is sometimes applied to flamage, it more usually connotes derision for communication styles that e...
control-C => vi. 1. "Stop whatever you are doing." From the interrupt character used on many operating systems to abort a running program. Considered silly. 2. interj. Among BSD UNIX hackers, the canonical humorous response to "Give me a break!"
control-O => vi. "Stop talking." From the character used on some operating systems to abort output but allow the program to keep on running. Generally means that you are not interested in hearing anything more from that person, at least on that topic...
control-Q => vi. "Resume." From the ASCII XON character used to undo a previous control-S (in fact it is also pronounced XON /X-on/).
control-S => vi. "Stop talking for a second." From the ASCII XOFF character (this is also pronounced XOFF /X-of/). Control-S differs from control-O in that the person is asked to stop talking (perhaps because you are on the phone) but will be allowed...
Conway's Law => prov. The rule that the organization of the software and the organization of the software team will be congruent; originally stated as "If you have four groups working on a compiler, you'll get a 4-pass compiler". This was originally ...
Conway's Law2 => early proto-hacker who wrote an assembler for the Burroughs 220 called SAVE. The name `SAVE' didn't stand for anything; it was just that you lost fewer card decks and listings because they all had SAVE written on them. 
cookbook => [from amateur electronics and radio] n. A book of small code segments that the reader can use to do various magic things in programs. One current example is the `PostScript Language Tutorial and Cookbook' by Adobe Systems, Inc (Addison-We...
cookie => n. A handle, transaction ID, or other token of agreement between cooperating programs. "I give him a packet, he gives me back a cookie." The claim check you get from a dry-cleaning shop is a perfect mundane example of a cookie; the only thi...
cookie bear => n. Syn. {cookie monster}.
cookie file => n. A collection of {fortune cookie}s in a format that facilitates retrieval by a fortune program. There are several different ones in public distribution, and site admins often assemble their own from various sources including this lex...
cookie monster => [from "Sesame Street"] n. Any of a family of early (1970s) hacks reported on {TOPS-10}, {ITS}, {Multics}, and elsewhere that would lock up either the victim's terminal (on a time-sharing machine) or the {console} (on a batch mainfra...
cookie monster2 => "I WANT A COOKIE". The required responses ranged in complexity from "COOKIE" through "HAVE A COOKIE" and upward. See also wabbit. 
copper => n. Conventional electron-carrying network cable with a core conductor of copper --- or aluminum! Opposed to {light pipe} or, say, a short-range microwave link.
copy protection => n. A class of clever methods for preventing incompetent pirates from stealing software and legitimate customers from using it. Considered silly.
copybroke => /ko'pee-brohk/ adj. [play on `copyright'] Used to describe an instance of a copy-protected program that has been `broken'; that is, a copy with the copy-protection scheme disabled. Syn. copywronged.
copyleft => /kop'ee-left/ [play on `copyright'] n. 1. The copyright notice (`General Public License') carried by GNU EMACS and other Free Software Foundation software, granting reuse and reproduction rights to all comers (but see also {General Public...
copywronged => /ko'pee-rongd/ [play on `copyright'] adj. Syn. for copybroke.
core => n. Main storage or RAM. Dates from the days of ferrite-core memory; now archaic as techspeak most places outside IBM, but also still used in the UNIX community and by old-time hackers or those who would sound like them. Some derived idioms ar...
core dump => n. [common {Iron Age} jargon, preserved by UNIX] 1. [techspeak] A copy of the contents of core, produced when a process is aborted by certain kinds of internal error. 2. By extension, used for humans passing out, vomiting, or registering...
core dump2 => All over the floor. What a mess." "He heard about X and dumped core." 3. Occasionally used for a human rambling on pointlessly at great length; esp. in apology "Sorry, I dumped core on you". 4. A recapitulation of knowledge (compare bit...
core dump3 => one knows about a topic, esp. in a lecture or answer to an exam question. "Short, concise answers are better than core dumps" (from the instructions to an exam at Columbia; syn. {brain dump}). See core. 
core leak => n. Syn. {memory leak}.
Core Wars => n. A game between `assembler' programs in a simulated machine, where the objective is to kill your opponent's program by overwriting it. Popularized by A. K. Dewdney's column in `Scientific American' magazine, this was actually devised b...
Core Wars2 => and Dennis Ritchie in the early 1960s (their original game was called `Darwin' and ran on a PDP-1 at Bell Labs). See core. 
corge => /korj/ [originally, the name of a cat] n. Yet another meta-syntactic variable, invented by Mike Gallaher and propagated by the GOSMACS documentation. See grault.
cosmic rays => n. Notionally, the cause of {bit rot}. However, this is a semi-independent usage that may be invoked as a humorous way to handwave away any minor randomness that doesn't seem worth the bother of investigating. "Hey, Eric --- I just got...
cosmic rays2 => tube, where did that come from?" "Cosmic rays, I guess." Compare sunspots, {phase of the moon}. The British seem to prefer the usage `cosmic showers'; `alpha particles' is also heard, because stray alpha particles passing through a me...
cosmic rays3 => errors (this becomes increasingly more likely as memory sizes and densities increase). Factual note Alpha particles cause bit rot, cosmic rays do not (except occasionally in spaceborne computers). Intel could not explain random bit dr...
cosmic rays4 => hypothesis was cosmic rays. So they created the World's Largest Lead Safe, using 25 tons of the stuff, and used two identical boards for testing. One was placed in the safe, one outside. The hypothesis was that if cosmic rays were cau...
cosmic rays5 => a statistically significant difference between the error rates on the two boards. They did not observe such a difference. Further investigation demonstrated conclusively that the bit drops were due to alpha particle emissions from tho...
cosmic rays6 => uranium) in the encapsulation material. Since it is impossible to eliminate these radioactives (they are uniformly distributed through the earth's crust, with the statistically insignificant exception of uranium lodes) it became obvio...
cosmic rays7 => to withstand these hits. 
cough and die => v. Syn. barf. Connotes that the program is throwing its hands up by design rather than because of a bug or oversight. "The parser saw a control-A in its input where it was looking for a printable, so it coughed and died."
cowboy => [Sun, from William Gibson's cyberpunk SF] n. Synonym for hacker. It is reported that at Sun this word is often said with reverence.
CP/M => /C-P-M/ n. [Control Program for Microcomputers] An early microcomputer OS written by hacker Gary Kildall for 8080- and Z80-based machines, very popular in the late 1970s but virtually wiped out by MS-DOS after the release of the IBM PC in 198...
CPU Wars => /C-P-U worz/ n. A 1979 large-format comic by Chas Andres chronicling the attempts of the brainwashed androids of IPM (Impossible to Program Machines) to conquer and destroy the peaceful denizens of HEC (Human Engineered Computers). This r...
CPU Wars2 => many references to ADVENT and the immortal line "Eat flaming death, minicomputer mongrels!" (uttered, of course, by an IPM stormtrooper). It is alleged that the author subsequently received a letter of appreciation on IBM company station...
CPU Wars3 => J. Watson Research Laboratories (then, as now, one of the few islands of true hackerdom in the IBM archipelago). The lower loop of the B in the IBM logo, it is said, had been carefully whited out. See {eat flaming death}. 
cracker => n. One who breaks security on a system. Coined ca. 1985 by hackers in defense against journalistic misuse of hacker (q.v., sense 8). An earlier attempt to establish `worm' in this sense around 1981--82 on USENET was largely a failure.
crank => [from automotive slang] vt. Verb used to describe the performance of a machine, especially sustained performance. "This box cranks (or, cranks at) about 6 megaflops, with a burst mode of twice that on vectorized operations."
crash => 1. n. A sudden, usually drastic failure. Most often said of the system (q.v., sense 1), sometimes of magnetic disk drives. "Three lusers lost their files in last night's disk crash." A disk crash that involves the read/write heads dropping o...
crash and burn => vi.,n. A spectacular crash, in the mode of the conclusion of the car-chase scene in the movie "Bullitt" and many subsequent imitators. Sun-3 monitors losing the flyback transformer and lightning strikes on VAX-11/780 backplanes are ...
crash and burn2 => The construction `crash-and-burn machine' is reported for a computer used exclusively for alpha or beta testing, or reproducing bugs (i.e., not for development). The implication is that it wouldn't be such a disaster if that machin...
crash and burn3 => would be inconvenienced. 
crawling horror => n. Ancient crufty hardware or software that is kept obstinately alive by forces beyond the control of the hackers at a site. Like {dusty deck} or gonkulator, but connotes that the thing described is not just an irritation but an ac...
crawling horror2 => "Mostly we code new stuff in C, but they pay us to maintain one big FORTRAN II application from nineteen-sixty-X that's a real crawling horror...." Compare WOMBAT. 
cray => /kray/ n. 1. (properly, capitalized) One of the line of supercomputers designed by Cray Research. 2. Any supercomputer at all. 3. The canonical number-crunching machine. The term is actually the lowercased last name of Seymour Cray, a noted c...
cray instability => n. A shortcoming of a program or algorithm that manifests itself only when a large problem is being run on a powerful machine (see cray). Generally more subtle than bugs that can be detected in smaller problems running on a workst...
crayola => /kray-oh'l*/ n. A super-mini or -micro computer that provides some reasonable percentage of supercomputer performance for an unreasonably low price. Might also be a {killer micro}.
crayon => n. 1. Someone who works on Cray supercomputers. More specifically, it implies a programmer, probably of the CDC ilk, probably male, and almost certainly wearing a tie (irrespective of gender). Systems types who have a UNIX background tend n...
creationism => n. The (false) belief that large, innovative designs can be completely specified in advance and then painlessly magicked out of the void by the normal efforts of a team of normally talented programmers. In fact, experience has shown re...
creeping elegance => n. Describes a tendency for parts of a design to become elegant past the point of diminishing return. This often happens at the expense of the less interesting parts of the design, the schedule, and other things deemed important ...
creeping elegance2 => {creeping featurism}, {second-system effect}, tense. 
creeping featurism => /kree'ping fee'chr-izm/ n. 1. Describes a systematic tendency to load more chrome and features onto systems at the expense of whatever elegance they may have possessed when originally designed. See also {feeping creaturism}. "Yo...
creeping featurism2 => BSD UNIX has always been creeping featurism." 2. More generally, the tendency for anything complicated to become even more complicated because people keep saying "Gee, it would be even better if it had this feature too". (See f...
creeping featurism3 => a patchwork because it grew one ad-hoc step at a time, rather than being planned. Planning is a lot of work, but it's easy to add just one extra little feature to help someone ... and then another ... and another.... When creep...
creeping featurism4 => like a cancer. Usually this term is used to describe computer programs, but it could also be said of the federal government, the IRS 1040 form, and new cars. A similar phenomenon sometimes afflicts conscious redesigns; see {sec...
creeping featuritis => /kree'ping fee'-chr-i`t*s/ n. Variant of {creeping featurism}, with its own spoonerization `feeping creaturitis'. Some people like to reserve this form for the disease as it actually manifests in software or hardware, as oppose...
creeping featuritis2 => designers' minds. (After all, -ism means `condition' or `pursuit of', whereas -itis usually means `inflammation of'.) 
cretin => /kret'n/ or /kree'tn/ n. Congenital loser; an obnoxious person; someone who can't do anything right. It has been observed that many American hackers tend to favor the British pronunciation /kre'tn/ over standard American /kree'tn/; it is th...
cretinous => /kret'n-*s/ or /kreet'n-*s/ adj. Wrong; stupid; non-functional; very poorly designed. Also used pejoratively of people. See {dread high-bit disease} for an example. Approximate synonyms bletcherous, `bagbiting' (see bagbiter), losing, br...
crippleware => n. 1. Software that has some important functionality deliberately removed, so as to entice potential users to pay for a working version. 2. [Cambridge] Guiltware that exhorts you to donate to some charity (compare careware). 3. Hardwar...
critical mass => n. In physics, the minimum amount of fissionable material required to sustain a chain reaction. Of a software product, describes a condition of the software such that fixing one bug introduces one plus epsilon bugs. When software ach...
critical mass2 => be discarded and rewritten. 
crlf => /ker'l*f/, sometimes /kru'l*f/ or /C-R-L-F/ n. (often capitalized as `CRLF') A carriage return (CR) followed by a line feed (LF). More loosely, whatever it takes to get you from the end of one line of text to the beginning of the next line. S...
crock => [from the obvious mainstream scatologism] n. 1. An awkward feature or programming technique that ought to be made cleaner. Using small integers to represent error codes without the program interpreting them to the user (as in, for example, U...
cross-post => [USENET] vi. To post a single article simultaneously to several newsgroups. Distinguished from posting the article repeatedly, once to each newsgroup, which causes people to see it multiple times (this is very bad form). Gratuitous cros...