classes ::: archetype,
children :::
branches ::: the Hacker

bookmarks: Instances - Definitions - Quotes - Chapters - Wordnet - Webgen


object:the Hacker
class:archetype

see also :::

questions, comments, suggestions/feedback, take-down requests, contribute, etc
contact me @ integralyogin@gmail.com or
join the integral discord server (chatrooms)
if the page you visited was empty, it may be noted and I will try to fill it out. cheers



now begins generated list of local instances, definitions, quotes, instances in chapters, wordnet info if available and instances among weblinks


OBJECT INSTANCES [0] - TOPICS - AUTHORS - BOOKS - CHAPTERS - CLASSES - SEE ALSO - SIMILAR TITLES

TOPICS
SEE ALSO


AUTH

BOOKS

IN CHAPTERS TITLE

IN CHAPTERS CLASSNAME

IN CHAPTERS TEXT

PRIMARY CLASS

archetype
SIMILAR TITLES
the Hacker

DEFINITIONS


TERMS STARTING WITH


TERMS ANYWHERE

April Fool's Joke "humour, event" (AFJ) Elaborate April Fool's hoaxes are a long-established tradition on {Usenet} and {Internet}; see {kremvax} for an example. In fact, April Fool's Day is the *only* seasonal holiday marked by customary observances on the hacker networks. (1995-01-25)

April Fool's Joke ::: (humour, event) (AFJ) Elaborate April Fool's hoaxes are a long-established tradition on Usenet and Internet; see kremvax for an example. In fact, April Fool's Day is the *only* seasonal holiday marked by customary observances on the hacker networks. (1995-01-25)

baz ::: /baz/ The third metasyntactic variable Suppose we have three functions: FOO, BAR, and BAZ. FOO calls BAR, which calls BAZ... (See also fum). Occasionally appended to foo to produce foobaz.Early versions of the Hacker Jargon dictionary derived baz as a Stanford corruption of bar. However, Pete Samson (compiler of the TMRC lexicon) reports counties of Rowrfolk and Bassex (Rowrbazzle mingled with Norfolk/Suffolk/Middlesex/ Essex).[Jargon File]

baz /baz/ The third {metasyntactic variable} "Suppose we have three functions: FOO, BAR, and BAZ. FOO calls BAR, which calls BAZ..." (See also {fum}). Occasionally appended to {foo} to produce "foobaz". Early versions of the Hacker Jargon dictionary derived "baz" as a Stanford corruption of {bar}. However, Pete Samson (compiler of the {TMRC} lexicon) reports it was already current when he joined TMRC in 1958. He says "It came from "Pogo". Albert the Alligator, when vexed or outraged, would shout "Bazz Fazz!" or "Rowrbazzle!" The club layout was said to model the (mythical) New England counties of Rowrfolk and Bassex (Rowrbazzle mingled with Norfolk/Suffolk/Middlesex/ Essex)." [{Jargon File}] (2008-06-30)

bulletin board system "communications, application" (BBS, bboard /bee'bord/, message board, forum; plural: BBSes) A computer and associated software which typically provides an electronic message database where people can log in and leave messages. Messages are typically split into {topic groups} similar to the {newsgroups} on {Usenet} (which is like a distributed BBS). Any user may submit or read any message in these public areas. The term comes from physical pieces of board on which people can pin messages written on paper for general consumption - a "physical bulletin board". {Ward Christensen}, the programmer and operator of the first BBS (on-line 1978-02-16) called it a CBBS for "computer bulletin board system". Since the rise of the {World-Wide Web}, the term has become antiquated, though the concept is more popular than ever, with many {websites} featuring discussion areas where users can post messages for public consumption. Apart from public message areas, some BBSes provided archives of files, personal {electronic mail} and other services of interest to the system operator ({sysop}). Thousands of BBSes around the world were run from amateurs' homes on {MS-DOS} boxes with a single {modem} line each. Although BBSes were traditionally the domain of hobbyists, many connected directly to the {Internet} (accessed via {telnet}), others were operated by government, educational, and research institutions. Fans of {Usenet} or the big commercial {time-sharing} bboards such as {CompuServe}, {CIX} and {GEnie} tended to consider local BBSes the low-rent district of the hacker culture, but they helped connect hackers and users in the personal-{micro} and let them exchange code. Use of this term for a {Usenet} newsgroup generally marks one either as a {newbie} fresh in from the BBS world or as a real old-timer predating {Usenet}. (2005-09-20)

crawling horror "jargon" 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 active menace to health and sanity. "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}. [{Jargon File}] (1994-12-01)

crawling horror ::: (jargon) 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 pay us to maintain one big Fortran II application from nineteen-sixty-X that's a real crawling horror.Compare WOMBAT.[Jargon File] (1994-12-01)

demigod "person" A hacker with years of experience, a national reputation, and a major role in the development of at least one design, tool, or game used by or known to more than half of the hacker community. To qualify as a genuine demigod, the person must recognisably identify with the hacker community and have helped shape it. Major demigods include {Ken Thompson} and {Dennis Ritchie} (co-inventors of {Unix} and {C}) and {Richard Stallman} (inventor of {Emacs}). In their hearts of hearts, most hackers dream of someday becoming demigods themselves, and more than one major software project has been driven to completion by the author's veiled hopes of apotheosis. See also {net.god}, {true-hacker}. [{Jargon File}] (1994-10-27)

DOS/360 ::: (operating system) The operating system announced by IBM at the low end for the System/360 in 1964 and delivered in 1965 or 1966.Following the failure of OS, IBM designed DOS for the low end machines, able to run in 16KB(?) and 64KB memory.DOS/360 used three memory partitions, but it had no serious memory protection. The three partitions were not specialised, but frequently one was used for spooling punched cards to disk, another one for batch job execution and another for spooling disk to printers.With DOS/VS, introduced in 1970, the number of partitions was increased, virtual memory was introduced and the minimum memory requirements increased.Later they released DOS/VSE and ESA/VSE. DOS/360 successors are still alive today (1997) though not as popular as in the late 1960s.Contrary to the Hacker's Jargon File, GECOS was not copied from DOS/360. (1997-09-22)

DOS/360 "operating system" The {operating system} announced by {IBM} at the low end for the {System/360} in 1964 and delivered in 1965 or 1966. Following the failure of {OS}, IBM designed DOS for the low end machines, able to run in 16KB(?) and 64KB memory. DOS/360 used three {memory partitions}, but it had no serious {memory protection}. The three partitions were not specialised, but frequently one was used for {spooling} {punched cards} to {disk}, another one for {batch job} execution and another for spooling disk to printers. With DOS/VS, introduced in 1970, the number of partitions was increased, {virtual memory} was introduced and the minimum memory requirements increased. Later they released DOS/VSE and ESA/VSE. DOS/360 successors are still alive today (1997) though not as popular as in the late 1960s. Contrary to the Hacker's {Jargon File}, {GECOS} was not copied from DOS/360. (1997-09-22)

DWIM /dwim/ [acronym, "Do What I Mean" (not what I say)] 1. Able to guess, sometimes even correctly, the result intended when bogus input was provided. 2. The BBNLISP/INTERLISP function that attempted to accomplish this feat by correcting many of the more common errors. See {hairy}. 3. Occasionally, an interjection hurled at a balky computer, especially when one senses one might be tripping over legalisms (see {legalese}). Warren Teitelman originally wrote DWIM to fix his typos and spelling errors, so it was somewhat idiosyncratic to his style, and would often make hash of anyone else's typos if they were stylistically different. Some victims of DWIM thus claimed that the acronym stood for "Damn Warren's Infernal Machine!'. In one notorious incident, Warren added a DWIM feature to the command interpreter used at {Xerox PARC}. One day another hacker there typed "delete *$" to free up some disk space. (The editor there named backup files by appending "$" to the original file name, so he was trying to delete any backup files left over from old editing sessions.) It happened that there weren't any editor backup files, so DWIM helpfully reported "*$ not found, assuming you meant 'delete *'". It then started to delete all the files on the disk! The hacker managed to stop it with a {Vulcan nerve pinch} after only a half dozen or so files were lost. The disgruntled victim later said he had been sorely tempted to go to Warren's office, tie Warren down in his chair in front of his workstation, and then type "delete *$" twice. DWIM is often suggested in jest as a desired feature for a complex program; it is also occasionally described as the single instruction the ideal computer would have. Back when proofs of program correctness were in vogue, there were also jokes about "DWIMC" (Do What I Mean, Correctly). A related term, more often seen as a verb, is DTRT (Do The Right Thing); see {Right Thing}. [{Jargon File}]

El Camino Bignum ::: (humour) /el' k*-mee'noh big'nuhm/ The road mundanely called El Camino Real, a road through the San Francisco peninsula that originally extended all Real, which defines logical north and south even though it isn't really north-south many places. El Camino Real runs right past Stanford University.The Spanish word real (which has two syllables: /ray-al'/) means royal; El Camino Real is the royal road. In the Fortran language, a real quantity is a quantity is a larger floating-point number, precise to perhaps fourteen significant digits (other languages have similar real types).When a hacker from MIT visited Stanford in 1976, he remarked what a long road El Camino Real was. Making a pun on real, he started calling it El Camino Double Precision - but when the hacker was told that the road was hundreds of miles long, he renamed it El Camino Bignum, and that name has stuck. (See bignum).[Jargon File] (1996-07-16)

El Camino Bignum "humour" /el' k*-mee'noh big'nuhm/ The road mundanely called El Camino Real, a road through the San Francisco peninsula that originally extended all the way down to Mexico City and many portions of which are still intact. Navigation on the San Francisco peninsula is usually done relative to El Camino Real, which defines {logical} north and south even though it isn't really north-south many places. El Camino Real runs right past {Stanford University}. The Spanish word "real" (which has two syllables: /ray-al'/) means "royal"; El Camino Real is "the royal road". In the {Fortran} language, a "{real}" quantity is a number typically precise to seven significant digits, and a "{double precision}" quantity is a larger {floating-point} number, precise to perhaps fourteen significant digits (other languages have similar "real" types). When a {hacker} from {MIT} visited Stanford in 1976, he remarked what a long road El Camino Real was. Making a pun on "real", he started calling it "El Camino Double Precision" - but when the hacker was told that the road was hundreds of miles long, he renamed it "El Camino Bignum", and that name has stuck. (See {bignum}). [{Jargon File}] (1996-07-16)

Eric S. Raymond ::: (person) One of the authors of the Hacker's Jargon File. Eric was involved in the JOLT project and GNU Emacs as well as maintaining several FAQ lists. He is a keen advocate of open source. .E-mail: (1998-10-20)

Eric S. Raymond "person" One of the authors of the Hacker's {Jargon File}. Eric was involved in the {JOLT} project and {GNU Emacs} as well as maintaining several {FAQ} lists. He is a keen advocate of {open source}. {(http://ccil.org/~esr)}. E-mail: "esr@snark.thyrsus.com" (1998-10-20)

Flash Lights Impressively ::: (programming, command, humour) (FLI) /FLY/ A joke assembly language instruction first documented in the late 1970s in The Hackers Dictionary.The FLI instruction was frequently referred to by engineers when minicomputers such as the DEC PDP-8, PDP-11 and some early microcomputers such as the IMSAI and Altair had dozens of front panel lights.When the computer is about to do some long I/O operation, stick in a FLI so the accountants won't think the machine has hung again.(2004-08-23)

Flash Lights Impressively "programming, humour" (FLI) /FLY/ A joke {assembly language} instruction first documented in the late 1970s in "The Hackers Dictionary". The FLI instruction was frequently referred to by engineers when {minicomputers} such as the DEC {PDP-8}, {PDP-11} and some early {microcomputers} such as the {IMSAI} and {Altair} had dozens of front panel lights. "When the computer is about to do some long I/O operation, stick in a FLI so the accountants won't think the machine has hung again." (2004-08-23)

hacker ethic ::: (philosophy) 1. The belief that information-sharing is a powerful positive good, and that it is an ethical duty of hackers to share their expertise by writing free software and facilitating access to information and to computing resources wherever possible.2. The belief that system-cracking for fun and exploration is ethically OK as long as the cracker commits no theft, vandalism, or breach of confidentiality.Both of these normative ethical principles are widely, but by no means universally, accepted among hackers. Most hackers subscribe to the hacker ethic go further and assert that *all* information should be free and *any* proprietary control of it is bad; this is the philosophy behind the GNU project.Sense 2 is more controversial: some people consider the act of cracking itself to be unethical, like breaking and entering. But the belief that ethical how it was done and how the hole can be plugged - acting as an unpaid (and unsolicited) tiger team.The most reliable manifestation of either version of the hacker ethic is that almost all hackers are actively willing to share technical tricks, software, and reinforce a sense of community that may be hackerdom's most valuable intangible asset. (1995-12-18)

hacker ethic "philosophy" 1. The belief that information-sharing is a powerful positive good, and that it is an ethical duty of hackers to share their expertise by writing free software and facilitating access to information and to computing resources wherever possible. 2. The belief that system-cracking for fun and exploration is ethically OK as long as the cracker commits no theft, vandalism, or breach of confidentiality. Both of these normative ethical principles are widely, but by no means universally, accepted among hackers. Most hackers subscribe to the hacker ethic in sense 1, and many act on it by writing and giving away free software. A few go further and assert that *all* information should be free and *any* proprietary control of it is bad; this is the philosophy behind the {GNU} project. Sense 2 is more controversial: some people consider the act of cracking itself to be unethical, like breaking and entering. But the belief that "ethical" cracking excludes destruction at least moderates the behaviour of people who see themselves as "benign" crackers (see also {samurai}). On this view, it may be one of the highest forms of hackerly courtesy to (a) break into a system, and then (b) explain to the sysop, preferably by e-mail from a {superuser} account, exactly how it was done and how the hole can be plugged - acting as an unpaid (and unsolicited) {tiger team}. The most reliable manifestation of either version of the hacker ethic is that almost all hackers are actively willing to share technical tricks, software, and (where possible) computing resources with other hackers. Huge cooperative networks such as {Usenet}, {FidoNet} and Internet (see {Internet address}) can function without central control because of this trait; they both rely on and reinforce a sense of community that may be hackerdom's most valuable intangible asset. (1995-12-18)

hacker ::: (person, jargon) (Originally, someone who makes furniture with an axe) 1. A person who enjoys exploring the details of programmable systems and how to stretch their capabilities, as opposed to most users, who prefer to learn only the minimum necessary.2. One who programs enthusiastically (even obsessively) or who enjoys programming rather than just theorizing about programming.3. A person capable of appreciating hack value.4. A person who is good at programming quickly.5. An expert at a particular program, or one who frequently does work using it or on it; as in a Unix hacker. (Definitions 1 through 5 are correlated, and people who fit them congregate.)6. An expert or enthusiast of any kind. One might be an astronomy hacker, for example.7. One who enjoys the intellectual challenge of creatively overcoming or circumventing limitations.8. (Deprecated) A malicious meddler who tries to discover sensitive information by poking around. Hence password hacker, network hacker. The correct term is cracker.The term hacker also tends to connote membership in the global community defined by the net (see The Network and Internet address). It also implies that the person described is seen to subscribe to some version of the hacker ethic.It is better to be described as a hacker by others than to describe oneself that way. Hackers consider themselves something of an elite (a meritocracy based on gratifying to be called a hacker, false claimants to the title are quickly labelled as bogus or a wannabee.9. (University of Maryland, rare) A programmer who does not understand proper programming techniques and principles and doesn't have a Computer Science example, This program is nothing but spaghetti code. It must have been written by a hacker.[Jargon File] (1996-08-26)

hackish "jargon" /hak'ish/ 1. Said of something that is or involves a {hack}. 2. Of or pertaining to {hackers} or the hacker subculture. See also {true-hacker}. [{Jargon File}] (1995-03-08)

hackish ::: (jargon) /hak'ish/ 1. Said of something that is or involves a hack.2. Of or pertaining to hackers or the hacker subculture.See also true-hacker.[Jargon File] (1995-03-08)

ITS 1. Incompatible {time-sharing} System An influential but highly idiosyncratic {operating system} written for the {PDP-6} and {PDP-10} at {MIT} and long used at the {MIT AI Lab}. Much AI-hacker jargon derives from ITS folklore, and to have been "an ITS hacker" qualifies one instantly as an old-timer of the most venerable sort. ITS pioneered many important innovations, including transparent file sharing between machines and terminal-independent I/O. After about 1982, most actual work was shifted to newer machines, with the remaining ITS boxes run essentially as a hobby and service to the hacker community. The shutdown of the lab's last ITS machine in May 1990 marked the end of an era and sent old-time hackers into mourning nationwide (see {high moby}). The Royal Institute of Technology in Sweden is maintaining one "live" ITS site at its computer museum (right next to the only {TOPS-10} system still on the {Internet}), so ITS is still alleged to hold the record for OS in longest continuous use (however, {WAITS} is a credible rival for this palm). 2. A mythical image of {operating system} perfection worshiped by a bizarre, fervent retro-cult of old-time hackers and ex-users (see {troglodyte}). ITS worshipers manage somehow to continue believing that an OS maintained by {assembly language} hand-hacking that supported only monocase 6-character filenames in one directory per account remains superior to today's state of commercial art (their venom against {Unix} is particularly intense). See also {holy wars}, {Weenix}. [{Jargon File}] (1994-12-15)

lost in the underflow ::: (jargon) Too small to be worth considering; more specifically, small beyond the limits of accuracy or measurement. This is a reference to floating point underflow.The Hacker's Jargon File claimed that it is also a pun on undertow (a kind of fast, cold current that sometimes runs just offshore and can be dangerous to swimmers).Well, sure, photon pressure from the stadium lights alters the path of a thrown baseball, but that effect gets lost in the underflow.Compare epsilon, epsilon squared; see also overflow bit. (1997-09-05)

Mars ::: A legendary tragic failure, the archetypal Hacker Dream Gone Wrong. Mars was the code name for a family of PDP-10 compatible computers built by Systems Concepts DEC KL10, and ran all KL10 binaries (including the operating system) with no modifications at about 2--3 times faster than a KL10.When DEC cancelled the Jupiter project in 1983, Systems Concepts should have made a bundle selling their machine into shops with a lot of software investment excitement in the PDP-10 world. TOPS-10 was running on the Mars by the summer of 1984, and TOPS-20 by early fall.Unfortunately, the hackers running Systems Concepts were much better at designing machines than at mass producing or selling them; the company allowed other hungry startups building workstations with power comparable to the KL10 at a fraction of the price.By the time SC shipped the first SC-30M to Stanford in late 1985, most customers had already made the traumatic decision to abandon the PDP-10, usually for VMS or Unix boxes. Most of the Mars computers built ended up being purchased by CompuServe.This tale and the related saga of Foonly hold a lesson for hackers: if you want to play in the Real World, you need to learn Real World moves.[Jargon File]

Mars A legendary tragic failure, the archetypal Hacker Dream Gone Wrong. Mars was the code name for a family of PDP-10 compatible computers built by Systems Concepts (now, The SC Group): the multi-processor SC-30M, the small uniprocessor SC-25M, and the never-built superprocessor SC-40M. These machines were marvels of engineering design; although not much slower than the unique {Foonly} F-1, they were physically smaller and consumed less power than the much slower DEC KS10 or Foonly F-2, F-3, or F-4 machines. They were also completely compatible with the DEC KL10, and ran all KL10 binaries (including the operating system) with no modifications at about 2--3 times faster than a KL10. When DEC cancelled the Jupiter project in 1983, Systems Concepts should have made a bundle selling their machine into shops with a lot of software investment in PDP-10s, and in fact their spring 1984 announcement generated a great deal of excitement in the PDP-10 world. {TOPS-10} was running on the Mars by the summer of 1984, and {TOPS-20} by early fall. Unfortunately, the hackers running Systems Concepts were much better at designing machines than at mass producing or selling them; the company allowed itself to be sidetracked by a bout of perfectionism into continually improving the design, and lost credibility as delivery dates continued to slip. They also overpriced the product ridiculously; they believed they were competing with the KL10 and VAX 8600 and failed to reckon with the likes of Sun Microsystems and other hungry startups building workstations with power comparable to the KL10 at a fraction of the price. By the time SC shipped the first SC-30M to Stanford in late 1985, most customers had already made the traumatic decision to abandon the PDP-10, usually for VMS or Unix boxes. Most of the Mars computers built ended up being purchased by {CompuServe}. This tale and the related saga of {Foonly} hold a lesson for hackers: if you want to play in the {Real World}, you need to learn Real World moves. [{Jargon File}]

nanotechnology ::: /nan'-oh-tek-nol*-jee/ Any fabrication technology in which objects are designed and built by the specification and placement of individual atoms or molecules or where at least one dimension is on a scale of nanometers.The first unequivocal nanofabrication experiments took place in 1990, for example with the deposition of individual xenon atoms on a nickel substrate to spell the logo of a certain very large computer company.Nanotechnology has been a hot topic in the hacker subculture ever since the term was coined by K. Eric Drexler in his book Engines of Creation, where he predicted that nanotechnology could give rise to replicating assemblers, permitting an exponential growth of productivity and personal wealth.See also nanobot. .(2003-05-02)

phreaking "jargon" /freek'ing/ "phone phreak" 1. The art and science of {cracking} the telephone network so as, for example, to make free long-distance calls. 2. By extension, security-{cracking} in any other context (especially, but not exclusively, on communications networks). At one time phreaking was a semi-respectable activity among hackers; there was a gentleman's agreement that phreaking as an intellectual game and a form of exploration was OK, but serious theft of services was taboo. There was significant crossover between the hacker community and the hard-core phone phreaks who ran semi-underground networks of their own through such media as the legendary "TAP Newsletter". This ethos began to break down in the mid-1980s as wider dissemination of the techniques put them in the hands of less responsible phreaks. Around the same time, changes in the phone network made old-style technical ingenuity less effective as a way of hacking it, so phreaking came to depend more on overtly criminal acts such as stealing phone-card numbers. The crimes and punishments of gangs like the "414 group" turned that game very ugly. A few old-time hackers still phreak casually just to keep their hand in, but most these days have hardly even heard of "blue boxes" or any of the other paraphernalia of the great phreaks of yore. [{Jargon File}] (1994-11-09)

Pronunciation In this dictionary slashes (/../) bracket phonetic pronunciations of words not found in a standard English dictionary. The notation, and many of the pronunciations, were adapted from the Hacker's {Jargon File}. Syllables are separated by {dash} or followed {single quote} or {back quote}. Single quote means the preceding syllable is stressed (louder), back quote follows a syllable with intermediate stress (slightly louder), otherwise all syllables are equally stressed. Consonants are pronounced as in English but note: ch soft, as in "church" g hard, as in "got" gh aspirated g+h of "bughouse" or "ragheap" j voiced, as in "judge" kh guttural of "loch" or "l'chaim" s unvoiced, as in "pass" zh as "s" in "pleasure" Uppercase letters are pronounced as their English letter names; thus (for example) /H-L-L/ is equivalent to /aych el el/. /Z/ is pronounced /zee/ in the US and /zed/ in the UK (elsewhere?). Vowels are represented as follows: a back, that ah father, palm (see note) ar far, mark aw flaw, caught ay bake, rain e less, men ee easy, ski eir their, software i trip, hit i: life, sky o block, stock (see note) oh flow, sew oo loot, through or more, door ow out, how oy boy, coin uh but, some u put, foot *r   fur, insert (only in stressed syllables; otherwise use just "r") y yet, young yoo few, chew [y]oo /oo/ with optional fronting as in `news' (/nooz/ or /nyooz/) A /*/ is used for the `schwa' sound of unstressed or occluded vowels (often written with an upside-down `e'). The schwa vowel is omitted in unstressed syllables containing vocalic l, m, n or r; that is, "kitten" and "colour" would be rendered /kit'n/ and /kuhl'r/, not /kit'*n/ and /kuhl'*r/. The above table reflects mainly distinctions found in standard American English (that is, the neutral dialect spoken by TV network announcers and typical of educated speech in the Upper Midwest, Chicago, Minneapolis/St.Paul and Philadelphia). However, we separate /o/ from /ah/, which tend to merge in standard American. This may help readers accustomed to accents resembling British Received Pronunciation. Entries with a pronunciation of `//' are written-only. (1997-12-10)

Pronunciation ::: In this dictionary slashes (/../) bracket phonetic pronunciations of words not found in a standard English dictionary. The notation, and many of the pronunciations, were adapted from the Hacker's Jargon File.Syllables are separated by dash or followed single quote or back quote. Single quote means the preceding syllable is stressed (louder), back quote follows a syllable with intermediate stress (slightly louder), otherwise all syllables are equally stressed.Consonants are pronounced as in English but note: ch soft, as in churchg hard, as in got is pronounced /zee/ in the US and /zed/ in the UK (elsewhere?).Vowels are represented as follows: a back, thatah father, palm (see note) would be rendered /kit'n/ and /kuhl'r/, not /kit'*n/ and /kuhl'*r/.The above table reflects mainly distinctions found in standard American English (that is, the neutral dialect spoken by TV network announcers and typical of standard American. This may help readers accustomed to accents resembling British Received Pronunciation.Entries with a pronunciation of `//' are written-only. (1997-12-10)

pseudoprime A backgammon prime (six consecutive occupied points) with one point missing. This term is an esoteric pun derived from a mathematical method that, rather than determining precisely whether a number is prime (has no divisors), uses a statistical technique to decide whether the number is "probably" prime. A number that passes this test is called a pseudoprime. The hacker backgammon usage stems from the idea that a pseudoprime is almost as good as a prime: it does the job of a prime until proven otherwise, and that probably won't happen. [{Jargon File}]

random ::: 1. Unpredictable (closest to mathematical definition); weird. The system's been behaving pretty randomly.2. Assorted; undistinguished. Who was at the conference? Just a bunch of random business types.3. (pejorative) Frivolous; unproductive; undirected. He's just a random loser.4. Incoherent or inelegant; poorly chosen; not well organised. The program has a random set of misfeatures. That's a random name for that function. Well, all the names were chosen pretty randomly.5. In no particular order, though deterministic. The I/O channels are in a pool, and when a file is opened one is chosen randomly.6. Arbitrary. It generates a random name for the scratch file.7. Gratuitously wrong, i.e. poorly done and for no good apparent reason. For example, a program that handles file name defaulting in a particularly useless so that no one else can invoke it without first saving four extra registers. What randomness!8. A random hacker; used particularly of high-school students who soak up computer time and generally get in the way.9. Anyone who is not a hacker (or, sometimes, anyone not known to the hacker speaking). I went to the talk, but the audience was full of randoms asking bogus questions.10. (occasional MIT usage) One who lives at Random Hall. See also J. Random, some random X.[Jargon File] (1995-12-05)

random 1. Unpredictable (closest to mathematical definition); weird. "The system's been behaving pretty randomly." 2. Assorted; undistinguished. "Who was at the conference?" "Just a bunch of random business types." 3. (pejorative) Frivolous; unproductive; undirected. "He's just a random loser." 4. Incoherent or inelegant; poorly chosen; not well organised. "The program has a random set of misfeatures." "That's a random name for that function." "Well, all the names were chosen pretty randomly." 5. In no particular order, though {deterministic}. "The I/O channels are in a pool, and when a file is opened one is chosen randomly." 6. Arbitrary. "It generates a random name for the scratch file." 7. Gratuitously wrong, i.e. poorly done and for no good apparent reason. For example, a program that handles file name defaulting in a particularly useless way, or an assembler routine that could easily have been coded using only three registers, but redundantly uses seven for values with non-overlapping lifetimes, so that no one else can invoke it without first saving four extra registers. What {randomness}! 8. A random hacker; used particularly of high-school students who soak up computer time and generally get in the way. 9. Anyone who is not a hacker (or, sometimes, anyone not known to the hacker speaking). "I went to the talk, but the audience was full of randoms asking bogus questions". 10. (occasional MIT usage) One who lives at Random Hall. See also {J. Random}, {some random X}. [{Jargon File}] (1995-12-05)

Real Programmers Don't Use Pascal ::: (humour) Back in the good old days - the Golden Era of computers, it was easy to separate the men from the boys (sometimes called Real Men and out that Real Men don't relate to anything, and aren't afraid of being impersonal.)But, as usual, times change. We are faced today with a world in which little old ladies can get computers in their microwave ovens, 12-year-old kids can blow danger of becoming extinct, of being replaced by high-school students with TRASH-80s.There is a clear need to point out the differences between the typical high-school junior Pac-Man player and a Real Programmer. If this difference is why it would be a mistake to replace the Real Programmers on their staff with 12-year-old Pac-Man players (at a considerable salary savings).LANGUAGESThe easiest way to tell a Real Programmer from the crowd is by the programming language he (or she) uses. Real Programmers use Fortran. Quiche Eaters use need all these abstract concepts to get their jobs done - they are perfectly happy with a keypunch, a Fortran IV compiler, and a beer.Real Programmers do List Processing in Fortran.Real Programmers do String Manipulation in Fortran.Real Programmers do Accounting (if they do it at all) in Fortran.Real Programmers do Artificial Intelligence programs in Fortran.If you can't do it in Fortran, do it in assembly language. If you can't do it in assembly language, it isn't worth doing.STRUCTURED PROGRAMMINGThe academics in computer science have gotten into the structured programming rut over the past several years. They claim that programs are more easily in the world won't help you solve a problem like that - it takes actual talent. Some quick observations on Real Programmers and Structured Programming:Real Programmers aren't afraid to use GOTOs.Real Programmers can write five-page-long DO loops without getting confused.Real Programmers like Arithmetic IF statements - they make the code more interesting.Real Programmers write self-modifying code, especially if they can save 20 nanoseconds in the middle of a tight loop.Real Programmers don't need comments - the code is obvious.Since Fortran doesn't have a structured IF, REPEAT ... UNTIL, or CASE statement, Real Programmers don't have to worry about not using them. Besides, they can be simulated when necessary using assigned GOTOs.Data Structures have also gotten a lot of press lately. Abstract Data Types, Structures, Pointers, Lists, and Strings have become popular in certain circles. Languages, as we all know, have implicit typing based on the first letter of the (six character) variable name.OPERATING SYSTEMSWhat kind of operating system is used by a Real Programmer? CP/M? God forbid - CP/M, after all, is basically a toy operating system. Even little old ladies and grade school students can understand and use CP/M.Unix is a lot more complicated of course - the typical Unix hacker never can remember what the PRINT command is called this week - but when it gets right systems: they send jokes around the world on UUCP-net and write adventure games and research papers.No, your Real Programmer uses OS 370. A good programmer can find and understand the description of the IJK305I error he just got in his JCL manual. A great outstanding programmer can find bugs buried in a 6 megabyte core dump without using a hex calculator. (I have actually seen this done.)OS is a truly remarkable operating system. It's possible to destroy days of work with a single misplaced space, so alertness in the programming staff is people claim there is a Time Sharing system that runs on OS 370, but after careful study I have come to the conclusion that they were mistaken.PROGRAMMING TOOLSWhat kind of tools does a Real Programmer use? In theory, a Real Programmer could run his programs by keying them into the front panel of the computer. Back the first operating system for the CDC7600 in on the front panel from memory when it was first powered on. Seymore, needless to say, is a Real Programmer.One of my favorite Real Programmers was a systems programmer for Texas Instruments. One day he got a long distance call from a user whose system had includes a keypunch and lineprinter in his toolkit, he can get along with just a front panel and a telephone in emergencies.In some companies, text editing no longer consists of ten engineers standing in line to use an 029 keypunch. In fact, the building I work in doesn't contain a system is called SmallTalk, and would certainly not talk to the computer with a mouse.Some of the concepts in these Xerox editors have been incorporated into editors running on more reasonably named operating systems - Emacs and VI being two. The the Real Programmer wants a you asked for it, you got it text editor - complicated, cryptic, powerful, unforgiving, dangerous. TECO, to be precise.It has been observed that a TECO command sequence more closely resembles transmission line noise than readable text [4]. One of the more entertaining will probably destroy your program, or even worse - introduce subtle and mysterious bugs in a once working subroutine.For this reason, Real Programmers are reluctant to actually edit a program that is close to working. They find it much easier to just patch the binary object Programmer to do the job - no Quiche Eating structured programmer would even know where to start. This is called job security.Some programming tools NOT used by Real Programmers:Fortran preprocessors like MORTRAN and RATFOR. The Cuisinarts of programming - great for making Quiche. See comments above on structured programming.Source language debuggers. Real Programmers can read core dumps.Compilers with array bounds checking. They stifle creativity, destroy most of the interesting uses for EQUIVALENCE, and make it impossible to modify the operating system code with negative subscripts. Worst of all, bounds checking is inefficient.Source code maintenance systems. A Real Programmer keeps his code locked up in a card file, because it implies that its owner cannot leave his important programs unguarded [5].THE REAL PROGRAMMER AT WORKWhere does the typical Real Programmer work? What kind of programs are worthy of the efforts of so talented an individual? You can be sure that no Real or sorting mailing lists for People magazine. A Real Programmer wants tasks of earth-shaking importance (literally!).Real Programmers work for Los Alamos National Laboratory, writing atomic bomb simulations to run on Cray I supercomputers.Real Programmers work for the National Security Agency, decoding Russian transmissions.It was largely due to the efforts of thousands of Real Programmers working for NASA that our boys got to the moon and back before the Russkies.Real Programmers are at work for Boeing designing the operating systems for cruise missiles.Some of the most awesome Real Programmers of all work at the Jet Propulsion Laboratory in California. Many of them know the entire operating system of the bytes of unused memory in a Voyager spacecraft that searched for, located, and photographed a new moon of Jupiter.The current plan for the Galileo spacecraft is to use a gravity assist trajectory past Mars on the way to Jupiter. This trajectory passes within 80 +/-3 kilometers of the surface of Mars. Nobody is going to trust a Pascal program (or a Pascal programmer) for navigation to these tolerances.As you can tell, many of the world's Real Programmers work for the U.S. Government - mainly the Defense Department. This is as it should be. Recently, programmers and Quiche Eaters alike.) Besides, the determined Real Programmer can write Fortran programs in any language.The Real Programmer might compromise his principles and work on something slightly more trivial than the destruction of life as we know it, providing Fortran, so there are a fair number of people doing graphics in order to avoid having to write COBOL programs.THE REAL PROGRAMMER AT PLAYGenerally, the Real Programmer plays the same way he works - with computers. He is constantly amazed that his employer actually pays him to do what he would be breath of fresh air and a beer or two. Some tips on recognizing Real Programmers away from the computer room:At a party, the Real Programmers are the ones in the corner talking about operating system security and how to get around it.At a football game, the Real Programmer is the one comparing the plays against his simulations printed on 11 by 14 fanfold paper.At the beach, the Real Programmer is the one drawing flowcharts in the sand.At a funeral, the Real Programmer is the one saying Poor George, he almost had the sort routine working before the coronary.In a grocery store, the Real Programmer is the one who insists on running the cans past the laser checkout scanner himself, because he never could trust keypunch operators to get it right the first time.THE REAL PROGRAMMER'S NATURAL HABITATWhat sort of environment does the Real Programmer function best in? This is an important question for the managers of Real Programmers. Considering the amount of money it costs to keep one on the staff, it's best to put him (or her) in an environment where he can get his work done.The typical Real Programmer lives in front of a computer terminal. Surrounding this terminal are:Listings of all programs the Real Programmer has ever worked on, piled in roughly chronological order on every flat surface in the office.Some half-dozen or so partly filled cups of cold coffee. Occasionally, there will be cigarette butts floating in the coffee. In some cases, the cups will contain Orange Crush.Unless he is very good, there will be copies of the OS JCL manual and the Principles of Operation open to some particularly interesting pages.Taped to the wall is a line-printer Snoopy calendar for the year 1969.Strewn about the floor are several wrappers for peanut butter filled cheese bars - the type that are made pre-stale at the bakery so they can't get any worse while waiting in the vending machine.Hiding in the top left-hand drawer of the desk is a stash of double-stuff Oreos for special occasions.Underneath the Oreos is a flowcharting template, left there by the previous occupant of the office. (Real Programmers write programs, not documentation. Leave that to the maintenance people.)The Real Programmer is capable of working 30, 40, even 50 hours at a stretch, under intense pressure. In fact, he prefers it that way. Bad response time project done on time, but creates a convenient excuse for not doing the documentation. In general:No Real Programmer works 9 to 5 (unless it's the ones at night).Real Programmers don't wear neckties.Real Programmers don't wear high-heeled shoes.Real Programmers arrive at work in time for lunch [9].A Real Programmer might or might not know his wife's name. He does, however, know the entire ASCII (or EBCDIC) code table.Real Programmers don't know how to cook. Grocery stores aren't open at three in the morning. Real Programmers survive on Twinkies and coffee.THE FUTUREWhat of the future? It is a matter of some concern to Real Programmers that the latest generation of computer programmers are not being brought up with the same ever learning Fortran! Are we destined to become an industry of Unix hackers and Pascal programmers?From my experience, I can only report that the future is bright for Real Programmers everywhere. Neither OS 370 nor Fortran show any signs of dying out, one of them has a way of converting itself back into a Fortran 66 compiler at the drop of an option card - to compile DO loops like God meant them to be.Even Unix might not be as bad on Real Programmers as it once was. The latest release of Unix has the potential of an operating system worthy of any Real in - like having the best parts of Fortran and assembly language in one place. (Not to mention some of the more creative uses for

Real Programmers Don't Use Pascal "humour" Back in the good old days - the "Golden Era" of computers, it was easy to separate the men from the boys (sometimes called "Real Men" and "Quiche Eaters" in the literature). During this period, the Real Men were the ones that understood computer programming, and the Quiche Eaters were the ones that didn't. A real computer programmer said things like "DO 10 I=1,10" and "ABEND" (they actually talked in capital letters, you understand), and the rest of the world said things like "computers are too complicated for me" and "I can't relate to computers - they're so impersonal". (A previous work [1] points out that Real Men don't "relate" to anything, and aren't afraid of being impersonal.) But, as usual, times change. We are faced today with a world in which little old ladies can get computers in their microwave ovens, 12-year-old kids can blow Real Men out of the water playing Asteroids and Pac-Man, and anyone can buy and even understand their very own Personal Computer. The Real Programmer is in danger of becoming extinct, of being replaced by high-school students with {TRASH-80s}. There is a clear need to point out the differences between the typical high-school junior Pac-Man player and a Real Programmer. If this difference is made clear, it will give these kids something to aspire to -- a role model, a Father Figure. It will also help explain to the employers of Real Programmers why it would be a mistake to replace the Real Programmers on their staff with 12-year-old Pac-Man players (at a considerable salary savings). LANGUAGES The easiest way to tell a Real Programmer from the crowd is by the programming language he (or she) uses. Real Programmers use {Fortran}. Quiche Eaters use {Pascal}. Nicklaus Wirth, the designer of Pascal, gave a talk once at which he was asked how to pronounce his name. He replied, "You can either call me by name, pronouncing it 'Veert', or call me by value, 'Worth'." One can tell immediately from this comment that Nicklaus Wirth is a Quiche Eater. The only parameter passing mechanism endorsed by Real Programmers is call-by-value-return, as implemented in the {IBM 370} {Fortran-G} and H compilers. Real programmers don't need all these abstract concepts to get their jobs done - they are perfectly happy with a {keypunch}, a {Fortran IV} {compiler}, and a beer. Real Programmers do List Processing in Fortran. Real Programmers do String Manipulation in Fortran. Real Programmers do Accounting (if they do it at all) in Fortran. Real Programmers do {Artificial Intelligence} programs in Fortran. If you can't do it in Fortran, do it in {assembly language}. If you can't do it in assembly language, it isn't worth doing. STRUCTURED PROGRAMMING The academics in computer science have gotten into the "structured programming" rut over the past several years. They claim that programs are more easily understood if the programmer uses some special language constructs and techniques. They don't all agree on exactly which constructs, of course, and the examples they use to show their particular point of view invariably fit on a single page of some obscure journal or another - clearly not enough of an example to convince anyone. When I got out of school, I thought I was the best programmer in the world. I could write an unbeatable tic-tac-toe program, use five different computer languages, and create 1000-line programs that WORKED. (Really!) Then I got out into the Real World. My first task in the Real World was to read and understand a 200,000-line Fortran program, then speed it up by a factor of two. Any Real Programmer will tell you that all the Structured Coding in the world won't help you solve a problem like that - it takes actual talent. Some quick observations on Real Programmers and Structured Programming: Real Programmers aren't afraid to use {GOTOs}. Real Programmers can write five-page-long DO loops without getting confused. Real Programmers like Arithmetic IF statements - they make the code more interesting. Real Programmers write self-modifying code, especially if they can save 20 {nanoseconds} in the middle of a tight loop. Real Programmers don't need comments - the code is obvious. Since Fortran doesn't have a structured IF, REPEAT ... UNTIL, or CASE statement, Real Programmers don't have to worry about not using them. Besides, they can be simulated when necessary using {assigned GOTOs}. Data Structures have also gotten a lot of press lately. Abstract Data Types, Structures, Pointers, Lists, and Strings have become popular in certain circles. Wirth (the above-mentioned Quiche Eater) actually wrote an entire book [2] contending that you could write a program based on data structures, instead of the other way around. As all Real Programmers know, the only useful data structure is the Array. Strings, lists, structures, sets - these are all special cases of arrays and can be treated that way just as easily without messing up your programing language with all sorts of complications. The worst thing about fancy data types is that you have to declare them, and Real Programming Languages, as we all know, have implicit typing based on the first letter of the (six character) variable name. OPERATING SYSTEMS What kind of operating system is used by a Real Programmer? CP/M? God forbid - CP/M, after all, is basically a toy operating system. Even little old ladies and grade school students can understand and use CP/M. Unix is a lot more complicated of course - the typical Unix hacker never can remember what the PRINT command is called this week - but when it gets right down to it, Unix is a glorified video game. People don't do Serious Work on Unix systems: they send jokes around the world on {UUCP}-net and write adventure games and research papers. No, your Real Programmer uses OS 370. A good programmer can find and understand the description of the IJK305I error he just got in his JCL manual. A great programmer can write JCL without referring to the manual at all. A truly outstanding programmer can find bugs buried in a 6 megabyte {core dump} without using a hex calculator. (I have actually seen this done.) OS is a truly remarkable operating system. It's possible to destroy days of work with a single misplaced space, so alertness in the programming staff is encouraged. The best way to approach the system is through a keypunch. Some people claim there is a Time Sharing system that runs on OS 370, but after careful study I have come to the conclusion that they were mistaken. PROGRAMMING TOOLS What kind of tools does a Real Programmer use? In theory, a Real Programmer could run his programs by keying them into the front panel of the computer. Back in the days when computers had front panels, this was actually done occasionally. Your typical Real Programmer knew the entire bootstrap loader by memory in hex, and toggled it in whenever it got destroyed by his program. (Back then, memory was memory - it didn't go away when the power went off. Today, memory either forgets things when you don't want it to, or remembers things long after they're better forgotten.) Legend has it that {Seymore Cray}, inventor of the Cray I supercomputer and most of Control Data's computers, actually toggled the first operating system for the CDC7600 in on the front panel from memory when it was first powered on. Seymore, needless to say, is a Real Programmer. One of my favorite Real Programmers was a systems programmer for Texas Instruments. One day he got a long distance call from a user whose system had crashed in the middle of saving some important work. Jim was able to repair the damage over the phone, getting the user to toggle in disk I/O instructions at the front panel, repairing system tables in hex, reading register contents back over the phone. The moral of this story: while a Real Programmer usually includes a keypunch and lineprinter in his toolkit, he can get along with just a front panel and a telephone in emergencies. In some companies, text editing no longer consists of ten engineers standing in line to use an 029 keypunch. In fact, the building I work in doesn't contain a single keypunch. The Real Programmer in this situation has to do his work with a "text editor" program. Most systems supply several text editors to select from, and the Real Programmer must be careful to pick one that reflects his personal style. Many people believe that the best text editors in the world were written at Xerox Palo Alto Research Center for use on their Alto and Dorado computers [3]. Unfortunately, no Real Programmer would ever use a computer whose operating system is called SmallTalk, and would certainly not talk to the computer with a mouse. Some of the concepts in these Xerox editors have been incorporated into editors running on more reasonably named operating systems - {Emacs} and {VI} being two. The problem with these editors is that Real Programmers consider "what you see is what you get" to be just as bad a concept in Text Editors as it is in women. No the Real Programmer wants a "you asked for it, you got it" text editor - complicated, cryptic, powerful, unforgiving, dangerous. TECO, to be precise. It has been observed that a TECO command sequence more closely resembles transmission line noise than readable text [4]. One of the more entertaining games to play with TECO is to type your name in as a command line and try to guess what it does. Just about any possible typing error while talking with TECO will probably destroy your program, or even worse - introduce subtle and mysterious bugs in a once working subroutine. For this reason, Real Programmers are reluctant to actually edit a program that is close to working. They find it much easier to just patch the binary {object code} directly, using a wonderful program called SUPERZAP (or its equivalent on non-IBM machines). This works so well that many working programs on IBM systems bear no relation to the original Fortran code. In many cases, the original source code is no longer available. When it comes time to fix a program like this, no manager would even think of sending anything less than a Real Programmer to do the job - no Quiche Eating structured programmer would even know where to start. This is called "job security". Some programming tools NOT used by Real Programmers: Fortran preprocessors like {MORTRAN} and {RATFOR}. The Cuisinarts of programming - great for making Quiche. See comments above on structured programming. Source language debuggers. Real Programmers can read core dumps. Compilers with array bounds checking. They stifle creativity, destroy most of the interesting uses for EQUIVALENCE, and make it impossible to modify the operating system code with negative subscripts. Worst of all, bounds checking is inefficient. Source code maintenance systems. A Real Programmer keeps his code locked up in a card file, because it implies that its owner cannot leave his important programs unguarded [5]. THE REAL PROGRAMMER AT WORK Where does the typical Real Programmer work? What kind of programs are worthy of the efforts of so talented an individual? You can be sure that no Real Programmer would be caught dead writing accounts-receivable programs in {COBOL}, or sorting {mailing lists} for People magazine. A Real Programmer wants tasks of earth-shaking importance (literally!). Real Programmers work for Los Alamos National Laboratory, writing atomic bomb simulations to run on Cray I supercomputers. Real Programmers work for the National Security Agency, decoding Russian transmissions. It was largely due to the efforts of thousands of Real Programmers working for NASA that our boys got to the moon and back before the Russkies. Real Programmers are at work for Boeing designing the operating systems for cruise missiles. Some of the most awesome Real Programmers of all work at the Jet Propulsion Laboratory in California. Many of them know the entire operating system of the Pioneer and Voyager spacecraft by heart. With a combination of large ground-based Fortran programs and small spacecraft-based assembly language programs, they are able to do incredible feats of navigation and improvisation - hitting ten-kilometer wide windows at Saturn after six years in space, repairing or bypassing damaged sensor platforms, radios, and batteries. Allegedly, one Real Programmer managed to tuck a pattern-matching program into a few hundred bytes of unused memory in a Voyager spacecraft that searched for, located, and photographed a new moon of Jupiter. The current plan for the Galileo spacecraft is to use a gravity assist trajectory past Mars on the way to Jupiter. This trajectory passes within 80 +/-3 kilometers of the surface of Mars. Nobody is going to trust a Pascal program (or a Pascal programmer) for navigation to these tolerances. As you can tell, many of the world's Real Programmers work for the U.S. Government - mainly the Defense Department. This is as it should be. Recently, however, a black cloud has formed on the Real Programmer horizon. It seems that some highly placed Quiche Eaters at the Defense Department decided that all Defense programs should be written in some grand unified language called "ADA" ((C), DoD). For a while, it seemed that ADA was destined to become a language that went against all the precepts of Real Programming - a language with structure, a language with data types, {strong typing}, and semicolons. In short, a language designed to cripple the creativity of the typical Real Programmer. Fortunately, the language adopted by DoD has enough interesting features to make it approachable -- it's incredibly complex, includes methods for messing with the operating system and rearranging memory, and Edsgar Dijkstra doesn't like it [6]. (Dijkstra, as I'm sure you know, was the author of "GoTos Considered Harmful" - a landmark work in programming methodology, applauded by Pascal programmers and Quiche Eaters alike.) Besides, the determined Real Programmer can write Fortran programs in any language. The Real Programmer might compromise his principles and work on something slightly more trivial than the destruction of life as we know it, providing there's enough money in it. There are several Real Programmers building video games at Atari, for example. (But not playing them - a Real Programmer knows how to beat the machine every time: no challenge in that.) Everyone working at LucasFilm is a Real Programmer. (It would be crazy to turn down the money of fifty million Star Trek fans.) The proportion of Real Programmers in Computer Graphics is somewhat lower than the norm, mostly because nobody has found a use for computer graphics yet. On the other hand, all computer graphics is done in Fortran, so there are a fair number of people doing graphics in order to avoid having to write COBOL programs. THE REAL PROGRAMMER AT PLAY Generally, the Real Programmer plays the same way he works - with computers. He is constantly amazed that his employer actually pays him to do what he would be doing for fun anyway (although he is careful not to express this opinion out loud). Occasionally, the Real Programmer does step out of the office for a breath of fresh air and a beer or two. Some tips on recognizing Real Programmers away from the computer room: At a party, the Real Programmers are the ones in the corner talking about operating system security and how to get around it. At a football game, the Real Programmer is the one comparing the plays against his simulations printed on 11 by 14 fanfold paper. At the beach, the Real Programmer is the one drawing flowcharts in the sand. At a funeral, the Real Programmer is the one saying "Poor George, he almost had the sort routine working before the coronary." In a grocery store, the Real Programmer is the one who insists on running the cans past the laser checkout scanner himself, because he never could trust keypunch operators to get it right the first time. THE REAL PROGRAMMER'S NATURAL HABITAT What sort of environment does the Real Programmer function best in? This is an important question for the managers of Real Programmers. Considering the amount of money it costs to keep one on the staff, it's best to put him (or her) in an environment where he can get his work done. The typical Real Programmer lives in front of a computer terminal. Surrounding this terminal are: Listings of all programs the Real Programmer has ever worked on, piled in roughly chronological order on every flat surface in the office. Some half-dozen or so partly filled cups of cold coffee. Occasionally, there will be cigarette butts floating in the coffee. In some cases, the cups will contain Orange Crush. Unless he is very good, there will be copies of the OS JCL manual and the Principles of Operation open to some particularly interesting pages. Taped to the wall is a line-printer Snoopy calendar for the year 1969. Strewn about the floor are several wrappers for peanut butter filled cheese bars - the type that are made pre-stale at the bakery so they can't get any worse while waiting in the vending machine. Hiding in the top left-hand drawer of the desk is a stash of double-stuff Oreos for special occasions. Underneath the Oreos is a flowcharting template, left there by the previous occupant of the office. (Real Programmers write programs, not documentation. Leave that to the maintenance people.) The Real Programmer is capable of working 30, 40, even 50 hours at a stretch, under intense pressure. In fact, he prefers it that way. Bad response time doesn't bother the Real Programmer - it gives him a chance to catch a little sleep between compiles. If there is not enough schedule pressure on the Real Programmer, he tends to make things more challenging by working on some small but interesting part of the problem for the first nine weeks, then finishing the rest in the last week, in two or three 50-hour marathons. This not only impresses the hell out of his manager, who was despairing of ever getting the project done on time, but creates a convenient excuse for not doing the documentation. In general: No Real Programmer works 9 to 5 (unless it's the ones at night). Real Programmers don't wear neckties. Real Programmers don't wear high-heeled shoes. Real Programmers arrive at work in time for lunch [9]. A Real Programmer might or might not know his wife's name. He does, however, know the entire {ASCII} (or EBCDIC) code table. Real Programmers don't know how to cook. Grocery stores aren't open at three in the morning. Real Programmers survive on Twinkies and coffee. THE FUTURE What of the future? It is a matter of some concern to Real Programmers that the latest generation of computer programmers are not being brought up with the same outlook on life as their elders. Many of them have never seen a computer with a front panel. Hardly anyone graduating from school these days can do hex arithmetic without a calculator. College graduates these days are soft - protected from the realities of programming by source level debuggers, text editors that count parentheses, and "user friendly" operating systems. Worst of all, some of these alleged "computer scientists" manage to get degrees without ever learning Fortran! Are we destined to become an industry of Unix hackers and Pascal programmers? From my experience, I can only report that the future is bright for Real Programmers everywhere. Neither OS 370 nor Fortran show any signs of dying out, despite all the efforts of Pascal programmers the world over. Even more subtle tricks, like adding structured coding constructs to Fortran have failed. Oh sure, some computer vendors have come out with Fortran 77 compilers, but every one of them has a way of converting itself back into a Fortran 66 compiler at the drop of an option card - to compile DO loops like God meant them to be. Even Unix might not be as bad on Real Programmers as it once was. The latest release of Unix has the potential of an operating system worthy of any Real Programmer - two different and subtly incompatible user interfaces, an arcane and complicated teletype driver, virtual memory. If you ignore the fact that it's "structured", even 'C' programming can be appreciated by the Real Programmer: after all, there's no type checking, variable names are seven (ten? eight?) characters long, and the added bonus of the Pointer data type is thrown in - like having the best parts of Fortran and assembly language in one place. (Not to mention some of the more creative uses for

rotary debugger (Commodore) Essential equipment for those late-night or early-morning debugging sessions. Mainly used as sustenance for the hacker. Comes in many decorator colours, such as Sausage, Pepperoni, and Garbage. (1995-01-11)

rotary debugger ::: (Commodore) Essential equipment for those late-night or early-morning debugging sessions. Mainly used as sustenance for the hacker. Comes in many decorator colours, such as Sausage, Pepperoni, and Garbage. (1995-01-11)

samurai A hacker who hires out for legal cracking jobs, snooping for factions in corporate political fights, lawyers pursuing privacy-rights and First Amendment cases, and other parties with legitimate reasons to need an electronic locksmith. In 1991, mainstream media reported the existence of a loose-knit culture of samurai that meets electronically on BBS systems, mostly bright teenagers with personal micros; they have modelled themselves explicitly on the historical samurai of Japan and on the "net cowboys" of William Gibson's {cyberpunk} novels. Those interviewed claim to adhere to a rigid ethic of loyalty to their employers and to disdain the vandalism and theft practiced by criminal crackers as beneath them and contrary to the hacker ethic; some quote Miyamoto Musashi's "Book of Five Rings", a classic of historical samurai doctrine, in support of these principles. See also {Stupids}, {social engineering}, {cracker}, {hacker ethic}, and {dark-side hacker}. [{Jargon File}]

secondary damage ::: When a fatal error occurs (especially a segfault) the immediate cause may be that a pointer has been trashed due to a previous fandango on core. However, analysis will reveal (directly) how the damage occurred. The data structure was clobbered, but it was secondary damage.By extension, the corruption resulting from N cascaded fandangoes on core is Nth-level damage. There is at least one case on record in which 17 hours of seventh-level damage! The hacker who accomplished this near-superhuman feat was presented with an award by his fellows.[Jargon File]

secondary damage When a fatal error occurs (especially a {segfault}) the immediate cause may be that a pointer has been trashed due to a previous {fandango on core}. However, this fandango may have been due to an *earlier* fandango, so no amount of analysis will reveal (directly) how the damage occurred. "The data structure was clobbered, but it was secondary damage." By extension, the corruption resulting from N cascaded fandangoes on core is "Nth-level damage". There is at least one case on record in which 17 hours of {grovel}ling with "adb" actually dug up the underlying bug behind an instance of seventh-level damage! The hacker who accomplished this near-superhuman feat was presented with an award by his fellows. [{Jargon File}]

Share and enjoy! ::: 1. Commonly found at the end of software release announcements and README files, this phrase indicates allegiance to the hacker ethic of free information sharing (see hacker ethic).2. The motto of the Sirius Cybernetics Corporation (the ultimate gaggle of incompetent suits) in Douglas Adams's Hitch Hiker's Guide to the Galaxy. The irony of using this as a cultural recognition signal appeals to freeware hackers.[Jargon File]

Share and enjoy! 1. Commonly found at the end of software release announcements and {README files}, this phrase indicates allegiance to the hacker ethic of free information sharing (see {hacker ethic}). 2. The motto of the Sirius Cybernetics Corporation (the ultimate gaggle of incompetent {suits}) in Douglas Adams's "Hitch Hiker's Guide to the Galaxy". The irony of using this as a cultural recognition signal appeals to {freeware} hackers. [{Jargon File}]

snark ::: [Lewis Carroll, via the Michigan Terminal System] 1. A system failure. When a user's process bombed, the operator would get the message Help, Help, Snark in MTS!2. More generally, any kind of unexplained or threatening event on a computer (especially if it might be a boojum). Often used to refer to an event or a log file entry that might indicate an attempted security violation. See snivitz.3. UUCP name of snark.thyrsus.com, home site of the Hacker Jargon File versions 2.*.*.[Jargon File]

snark [Lewis Carroll, via the Michigan Terminal System] 1. A system failure. When a user's process bombed, the operator would get the message "Help, Help, Snark in MTS!" 2. More generally, any kind of unexplained or threatening event on a computer (especially if it might be a boojum). Often used to refer to an event or a log file entry that might indicate an attempted security violation. See {snivitz}. 3. UUCP name of snark.thyrsus.com, home site of the Hacker {Jargon File} versions 2.*.*. [{Jargon File}]

superprogrammer A prolific programmer; one who can code exceedingly well and quickly. Not all hackers are superprogrammers, but many are. Productivity can vary from one programmer to another by three orders of magnitude. For example, one programmer might be able to write an average of three lines of working code in one day, while another, with the proper tools, might be able to write 3,000. This range is astonishing; it is matched in very few other areas of human endeavour. The term "superprogrammer" is more commonly used within such places as IBM than in the hacker community. It tends to stress naive measures of productivity and to underweight creativity, ingenuity, and getting the job *done* - and to sidestep the question of whether the 3,000 lines of code do more or less useful work than three lines that do the {Right Thing}. Hackers tend to prefer the terms {hacker} and {wizard}. [{Jargon File}]

superprogrammer ::: A prolific programmer; one who can code exceedingly well and quickly. Not all hackers are superprogrammers, but many are. Productivity can vary from one while another, with the proper tools, might be able to write 3,000. This range is astonishing; it is matched in very few other areas of human endeavour.The term superprogrammer is more commonly used within such places as IBM than in the hacker community. It tends to stress naive measures of productivity and work than three lines that do the Right Thing. Hackers tend to prefer the terms hacker and wizard.[Jargon File]

TMRC /tmerk'/ The Tech Model Railroad Club at {MIT}, one of the wellsprings of {hacker} culture. The 1959 "Dictionary of the TMRC Language" compiled by Peter Samson included several terms that became basics of the hackish vocabulary (see especially {foo}, {mung}, and {frob}). By 1962, TMRC's legendary layout was already a marvel of complexity (and has grown in the thirty years since; all the features described here are still present). The control system alone featured about 1200 relays. There were {scram switch}es located at numerous places around the room that could be thwacked if something undesirable was about to occur, such as a train going full-bore at an obstruction. Another feature of the system was a digital clock on the dispatch board, which was itself something of a wonder in those bygone days before cheap LEDS and seven-segment displays. When someone hit a scram switch the clock stopped and the display was replaced with the word "FOO"; at TMRC the scram switches are therefore called "foo switches". Steven Levy, in his book "Hackers", gives a stimulating account of those early years. TMRC's Power and Signals group included most of the early {PDP-1} hackers and the people who later bacame the core of the {MIT} {AI Lab} staff. This dictionary accordingly includes a number of entries from the TMRC dictionary (via the Hacker Jargon File). [{Jargon File}] (2008-06-30)

TMRC ::: /tmerk'/ The Tech Model Railroad Club at MIT, one of the wellsprings of hacker culture. The 1959 Dictionary of the TMRC Language compiled by Peter Samson included several terms that became basics of the hackish vocabulary (see especially foo, mung, and frob).By 1962, TMRC's legendary layout was already a marvel of complexity (and has grown in the thirty years since; all the features described here are still stopped and the display was replaced with the word FOO; at TMRC the scram switches are therefore called foo switches.Steven Levy, in his book Hackers, gives a stimulating account of those early years. TMRC's Power and Signals group included most of the early PDP-1 hackers includes a number of entries from a recent revision of the TMRC dictionary (via the Hacker Jargon File).[Jargon File]

TWENEX ::: (operating system) /twe'neks/ The TOPS-20 operating system by DEC - the second proprietary OS for the PDP-10 - preferred by most PDP-10 hackers over krans meant funeral wreath in Swedish (though some Swedish speakers have since said it means simply wreath; this part of the story may be apocryphal).Ultimately DEC picked TOPS-20 as the name of the operating system, and it was as TOPS-20 that it was marketed. The hacker community, mindful of its origins, convert to VMS, but instead, by the late 1980s, most of the TOPS-20 hackers had migrated to Unix.[Jargon File] (1995-04-01)

TWENEX "operating system" /twe'neks/ The TOPS-20 {operating system} by {DEC} - the second proprietary OS for the {PDP-10} - preferred by most PDP-10 hackers over TOPS-10 (that is, by those who were not {ITS} or {WAITS} partisans). TOPS-20 began in 1969 as {Bolt, Beranek & Newman}'s {TENEX} operating system using special paging hardware. By the early 1970s, almost all of the systems on the {ARPANET} ran TENEX. DEC purchased the rights to TENEX from BBN and began work to make it their own. The first in-house code name for the operating system was VIROS (VIRtual memory Operating System); when customers started asking questions, the name was changed to SNARK so DEC could truthfully deny that there was any project called VIROS. When the name SNARK became known, the name was briefly reversed to become KRANS; this was quickly abandoned when someone objected that "krans" meant "funeral wreath" in Swedish (though some Swedish speakers have since said it means simply "wreath"; this part of the story may be apocryphal). Ultimately DEC picked TOPS-20 as the name of the operating system, and it was as TOPS-20 that it was marketed. The hacker community, mindful of its origins, quickly dubbed it TWENEX (a contraction of "twenty TENEX"), even though by this point very little of the original TENEX code remained (analogously to the differences between AT&T V6 Unix and BSD). DEC people cringed when they heard "TWENEX", but the term caught on nevertheless (the written abbreviation "20x" was also used). TWENEX was successful and very popular; in fact, there was a period in the early 1980s when it commanded as fervent a culture of partisans as Unix or ITS - but DEC's decision to scrap all the internal rivals to the VAX architecture and its relatively stodgy VMS OS killed the DEC-20 and put a sad end to TWENEX's brief day in the sun. DEC attempted to convince TOPS-20 users to convert to {VMS}, but instead, by the late 1980s, most of the TOPS-20 hackers had migrated to Unix. [{Jargon File}] (1995-04-01)

Virtual Memory System ::: (operating system) (VMS) DEC's proprietary operating system originally produced for its VAX minicomputer.VMS V1 was released in August 1978. VMS was renamed OpenVMS around version 5.5. The first version of VMS on DEC Alpha was known as OpenVMS for AXP V1.0, OpenVMS for Alpha. The renaming also signified the fact that the X/Open consortium had certified OpenVMS as having a high support for POSIX standards.VMS is one of the most secure operating systems on the market (making it popular in financial institutions). It currently (October 1997) has the best clustering capability (both number and distance) and is very scalable with binaries portable from small desktop workstations up to huge mainframes.Many Unix fans generously concede that VMS would probably be the hacker's favourite commercial OS if Unix didn't exist; though true, this makes VMS fans furious. .Usenet newsgroup: comp.os.vms.[How does its performance compare with other OSes?] (1999-06-03)

wannabee /won'*-bee/ (Or, more plausibly, spelled "wannabe") [Madonna fans who dress, talk, and act like their idol; probably originally from biker slang] A would-be {hacker}. The connotations of this term differ sharply depending on the age and exposure of the subject. Used of a person who is in or might be entering {larval stage}, it is semi-approving; such wannabees can be annoying but most hackers remember that they, too, were once such creatures. When used of any professional programmer, CS academic, writer, or {suit}, it is derogatory, implying that said person is trying to cuddle up to the hacker mystique but doesn't, fundamentally, have a prayer of understanding what it is all about. Overuse of hacker terms is often an indication of the {wannabee} nature. Compare {newbie}. Historical note: The wannabee phenomenon has a slightly different flavour now (1993) than it did ten or fifteen years ago. When the people who are now hackerdom's tribal elders were in {larval stage}, the process of becoming a hacker was largely unconscious and unaffected by models known in popular culture - communities formed spontaneously around people who, *as individuals*, felt irresistibly drawn to do hackerly things, and what wannabees experienced was a fairly pure, skill-focussed desire to become similarly wizardly. Those days of innocence are gone forever; society's adaptation to the advent of the microcomputer after 1980 included the elevation of the hacker as a new kind of folk hero, and the result is that some people semi-consciously set out to *be hackers* and borrow hackish prestige by fitting the popular image of hackers. Fortunately, to do this really well, one has to actually become a wizard. Nevertheless, old-time hackers tend to share a poorly articulated disquiet about the change; among other things, it gives them mixed feelings about the effects of public compendia of lore like this one. [{Jargon File}]



QUOTES [0 / 0 - 34 / 34]


KEYS (10k)


NEW FULL DB (2.4M)

   6 Steven Levy
   3 Kevin Mitnick
   2 Steven Johnson
   2 Parmy Olson
   2 Neal Stephenson
   2 Anonymous

*** WISDOM TROVE ***

*** NEWFULLDB 2.4M ***

1:Nothing is more disagreeable to the hacker than duplication of effort. ~ Anonymous,
2:if the hacker is a creator, we have to take inspiration into account. ~ Paul Graham,
3:in keeping with the Hacker Ethic, no artificial boundaries were maintained. ~ Steven Levy,
4:The hacker mindset doesn't actually see what happens on the other side, to the victim. ~ Kevin Mitnick,
5:the Hacker Ethic, which instructs you to keep working until your hack tops previous efforts. ~ Steven Levy,
6:The Yankees' Facebook page was hacked. The hacker was immediately purchased and signed to a 5 year contract with the Yankees. ~ Stephen Colbert,
7:The key to social engineering is influencing a person to do something that allows the hacker to gain access to information or your network. ~ Kevin Mitnick,
8:The Hacker Ethic: Access to computers--and anything which might teach you something about the way the world works--should be unlimited and total. ~ Steven Levy,
9:central tenets of the Hacker Ethic: the free flow of information, particularly information that helped fellow hackers understand, explore, and build systems. ~ Steven Levy,
10:The Hacker Way is an approach to building that involves continuous improvement and iteration. Hackers believe that something can always be better, and that nothing is ever complete. ~ Mark Zuckerberg,
11:fragile. So that to be able to defy a culture which states that ‘Thou shalt not touch this,’ and to defy that with one’s own creative powers is . . . the essence.” The essence, of course, of the Hacker Ethic. ~ Steven Levy,
12:The garage is the space for the hacker, the tinkerer, the maker. The garage is not defined by a single field or industry; instead, it is defined by the eclectic interests of its inhabitants. It is a space where intellectual networks converge. ~ Steven Johnson,
13:Years of working in the free-flow world of electronics had infused Marsh with the Hacker Ethic, and he saw school as an inefficient, repressive system. Even when he worked at a radical school with an open classroom, he thought it was a sham, still a jail. ~ Steven Levy,
14:It always seemed to me that the hacker occupied the same niche as the American cowboy in your Wild West. Gunslingers at the edge of known civilization. Black hats, white hats. Some drawn into thievery, others taking the law into their own hands—justice both corporeal and social. ~ Chuck Wendig,
15:When an attacker fails with one person, they often go to another person. The key is to report the attack to other departments. Workers should know to act like they are going along with what the hacker wants and take copious notes so the company will know what the hacker is trying to find. ~ Kevin Mitnick,
16:The Email Phishing Hack:  Phishing refers to a social engineering method used by hackers to gain what should be confidential information from unwitting victims. Phishing works in this way: the hacker sends an official-looking email to the target, purporting to be from the a legitimate institution that ~ Mike Mason,
17:A hacker is someone who enjoys playful cleverness—not necessarily with computers. The programmers in the old MIT free software community of the 60s and 70s referred to themselves as hackers. Around 1980, journalists who discovered the hacker community mistakenly took the term to mean “security breaker.” ~ Richard Stallman,
18:The fifth member of the team preferred to work at home. Ahmed was the hacker, the forger, the creator of all illusions, but he didn’t have the nerve to carry guns and such. He worked from his basement in Buffalo and had never been caught or arrested. He left no trails. His 5 percent would come off the top. The other four would take the rest in equal ~ John Grisham,
19:Nothing is more disagreeable to the hacker than duplication of effort. The first and most important mental habit that people develop when they learn how to write computer programs is to generalize, generalize, generalize. To make their code as modular and flexible as possible, breaking large problems down into small subroutines that can be used over and over again in different contexts. ~ Neal Stephenson,
20:Seeking evidence of the hacker spirit in antiquity, we must look no further than the mythic archetype of Prometheus. Zeus, father of the Gods, has forbidden to mankind the use of fire. Covertly entering Mt. Olympus, Prometheus liberates fire from the god’s abode and delivers it to man. Consequently, man nearly destroys himself with this powerful new technology and, in the process, dooms Prometheus to punishment for his actions. ~ Anonymous,
21:Now he was about to launch the Macintosh, a machine that violated many of the principles of the hacker’s code: It was overpriced; it would have no slots, which meant that hobbyists could not plug in their own expansion cards or jack into the motherboard to add their own new functions; and it took special tools just to open the plastic case. It was a closed and controlled system, like something designed by Big Brother rather than by a hacker. ~ Walter Isaacson,
22:The number 65,536 is an awkward figure to everyone except a hacker, who recognizes it more readily than his own mother's date of birth: It happens to be a power of 2—216 power to be exact—and even the exponent 16 is equal to 24, and 4 is equal to 22. Along with 256; 32,768; and 2,147,483,648; 65,536 is one of the foundation stones of the hacker universe, in which 2 is the only really important number because that's how many digits a computer can recognize. ~ Neal Stephenson,
23:Spacewar highlighted three aspects of the hacker culture that became themes of the digital age. First, it was created collaboratively. “We were able to build it together, working as a team, which is how we liked to do things,” Russell said. Second, it was free and open-source software. “People asked for copies of the source code, and of course we gave them out.” Of course—that was in a time and place when software yearned to be free. Third, it was based on the belief that computers should be personal and interactive. “It allowed us to get our hands on a computer and make it respond to us in real time,” said Russell.10 ~ Walter Isaacson,
24:Weizenbaum did not acknowledge the beauty of the hacker devotion itself...orthe very idealism of the Hacker Ethic. He had not seen, as Ed Fredkin had, Stew Nelson composing code on the TECO editor while Greenblatt and Gosper watched: without any of the three saying a word, Nelson was entertaining the others, encoding assembly-language tricks which to them, with their absolute mastery of that PDP-6 “language,” had the same effect as hilariously incisive jokes. And after every few instructions there would be another punch line in this sublime form of communication . . . The scene was a demonstration of sharing which Fredkin never forgot. ~ Anonymous,
25:Gosper had disdained NASA’s human-wave approach toward things. He had been adamant in defending the AI lab’s more individualistic form of hacker elegance in programming, and in computing style in general. But now he saw how the real world, when it got its mind made up, could have an astounding effect. NASA had not applied the Hacker Ethic, yet it had done something the lab, for all its pioneering, never could have done. Gosper realized that the ninth-floor hackers were in some sense deluding themselves, working on machines of relatively little power compared to the computers of the future — yet still trying to do it all, change the world right there in the lab. And ~ Steven Levy,
26:Unix is not so much a product as it is a painstakingly compiled oral history of the hacker subculture. It is our Gilgamesh epic: a living body of narrative that many people know by heart, and tell over and over again—making their own personal embellishments whenever it strikes their fancy. The bad embellishments are shouted down, the good ones picked up by others, polished, improved, and, over time, incorporated into the story. […] Thus Unix has slowly accreted around a simple kernel and acquired a kind of complexity and asymmetry about it that is organic, like the roots of a tree, or the branchings of a coronary artery. Understanding it is more like anatomy than physics. ~ Neal Stephenson,
27:An NSA unit known as the Transgression Branch specializes in this kind of track-the-hacker work and takes things one step further. The branch watches a hacker break into another country’s computer system, then follows him inside. In a 2010 operation called Ironavenger, the Transgression Branch saw e-mails containing malware being sent to a government office in a hostile country—one that the NSA wanted to know more about. Upon further inspection, the branch discovered that the malware was coming from a US ally, whose own intelligence service was trying to break in. The Americans let their allies do the hard work and watched silently as they scooped up passwords and sensitive documents from the adversary’s system. The Americans saw everything the allies saw and got some inside knowledge about how they spied. ~ Shane Harris,
28:Even back then I thought that his uncompromising judgments and unprompted opinions, which he would simply spit out undiplomatically, would put him at odds with a lot of people. There was so much to plan and discuss. I didn’t ask myself back then whether his behavior was normal or not. I didn’t ask myself whether I could trust Julian or whether he might get me in trouble. On the contrary, I was somewhat flattered that he was interested in working with me. For me, Julian Assange was not only the founder of WL but also the hacker known as Mendax, a member of the International Subversives, one of the greatest hackers in the world, and the coauthor/researcher (with Suelette Dreyfus) of Underground: Tales of Hacking, Madness and Obsession from the Electronic Frontier—a highly respected book among connoisseurs. We hit it off right from the start. He ~ Daniel Domscheit Berg,
29:If patterns of ones and zeros were “like” patterns of human lives and deaths, if everything about an individual could be represented in a computer record by a long string of ones and zeros, then what kind of creature would be represented by a long string of lives and deaths? It would have to be up one level at least—an angel, a minor god, something in a UFO. It would take eight human lives and deaths just to form one character in this being’s name—its complete dossier might take up a considerable piece of the history of the world. We are digits in God’s computer, she not so much thought as hummed to herself to a sort of standard gospel tune, And the only thing we’re good for, to be dead or to be living, is the only thing He sees. What we cry, what we contend for, in our world of toil and blood, it all lies beneath the notice of the hacker we call God. ~ Thomas Pynchon,
30:While the Texas prison officials remained in the dark about what was going on, they were fortunate that William and Danny had benign motives. Imagine what havoc the two might have caused; it would have been child's play for these guys to develop a scheme for obtaining money or property from unsuspecting victims. The Internet had become their university and playground. Learning how to run scams against individuals or break in to corporate sites would have been a cinch; teenagers and preteens learn these methods every day from the hacker sites and elsewhere on the Web. And as prisoners, Danny and William had all the time in the world.

Maybe there's a lesson here: Two convicted murderers, but that didn't mean they were scum, rotten to the core. They were cheaters who hacked their way onto the Internet illegally, but that didn't mean they were willing to victimize innocent people or naively insecure companies. ~ Kevin D Mitnick,
31:It would all be done with keys on alphanumeric keyboards that stood for weightless, invisible chains of electronic presence or absence. If patterns of ones and zeroes were "like" patterns of human lives and deaths, if everything about an individual could be represented in a computer record by a long strings of ones and zeroes, then what kind of creature could be represented by a long string of lives and deaths? It would have to be up one level, at least -- an angel, a minor god, something in a UFO. It would take eight human lives and deaths just to form one character in this being's name -- its complete dossier might take up a considerable piece of history of the world. We are digits in God's computer, she not so much thought as hummed to herself to sort of a standard gospel tune, And the only thing we're good for, to be dead or to be living, is the only thing He sees. What we cry, what we contend for, in our world of toil and blood, it all lies beneath the notice of the hacker we call God. ~ Thomas Pynchon,
32:values of commons-based sharing and of private enterprise often conflict, most notably over the extent to which innovations should be patent-protected. The commons crowd had its roots in the hacker ethic that emanated from the MIT Tech Model Railroad Club and the Homebrew Computer Club. Steve Wozniak was an exemplar. He went to Homebrew meetings to show off the computer circuit he built, and he handed out freely the schematics so that others could use and improve it. But his neighborhood pal Steve Jobs, who began accompanying him to the meetings, convinced him that they should quit sharing the invention and instead build and sell it. Thus Apple was born, and for the subsequent forty years it has been at the forefront of aggressively patenting and profiting from its innovations. The instincts of both Steves were useful in creating the digital age. Innovation is most vibrant in the realms where open-source systems compete with proprietary ones. Sometimes people advocate one of these modes of production over the others based on ideological sentiments. They prefer a greater government role, or exalt private enterprise, or romanticize peer sharing. In the 2012 election, President Barack Obama stirred up controversy by saying to people who owned businesses, “You didn’t build that.” His critics saw it as a denigration of the role of private enterprise. Obama’s point was that any business benefits from government and peer-based community support: “If you were successful, somebody along the line gave you some help. ~ Walter Isaacson,
33:The Lockean logic of custom suggests strongly that open-source hackers observe the customs they do in order to defend some kind of expected return from their effort. The return must be more significant than the effort of homesteading projects, the cost of maintaining version histories that document “chain of title”, and the time cost of making public notifications and waiting before taking adverse possession of an orphaned project. Furthermore, the “yield” from open source must be something more than simply the use of the software, something else that would be compromised or diluted by forking. If use were the only issue, there would be no taboo against forking, and open-source ownership would not resemble land tenure at all. In fact, this alternate world (where use is the only yield, and forking is unproblematic) is the one implied by existing open-source licenses. We can eliminate some candidate kinds of yield right away. Because you can’t coerce effectively over a network connection, seeking power is right out. Likewise, the open-source culture doesn’t have anything much resembling money or an internal scarcity economy, so hackers cannot be pursuing anything very closely analogous to material wealth (e.g. the accumulation of scarcity tokens). There is one way that open-source activity can help people become wealthier, however — a way that provides a valuable clue to what actually motivates it. Occasionally, the reputation one gains in the hacker culture can spill over into the real world in economically significant ways. It can get you a better job offer, or a consulting contract, or a book deal. This kind of side effect, however, is at best rare and marginal for most hackers; far too much so to make it convincing as a sole explanation, even if we ignore the repeated protestations by hackers that they’re doing what they do not for money but out of idealism or love. However, the way such economic side effects are mediated is worth examination. ~ Eric S Raymond,
34:It's ironic that Juanita has come into this place in a low-tech, black-and-white
avatar. She was the one who figured out a way to make avatars show something
close to real emotion. That is a fact Hiro has never forgotten, because she did
most of her work when they were together, and whenever an avatar looks surprised
or angry or passionate in the Metaverse, he sees an echo of himself or Juanita -
- the Adam and Eve of the Metaverse. Makes it hard to forget.
Shortly after Juanita and Da5id got divorced, The Black Sun really took off.
And once they got done counting their money, marketing the spinoffs, soaking up
the adulation of others in the hacker community, they all came to the
realization that what made this place a success was not the collision-avoidance
algorithms or the bouncer daemons or any of that other stuff. It was Juanita's
faces. Just ask the businessmen in the Nipponese Quadrant. They come here to
talk turkey with suits from around the world, and they consider it just as good
as a face-to-face. They more or less ignore what is being said -- a lot gets
lost in translation, after all. They pay attention to the facial expressions
and body language of the people they are talking to. And that's how they know
what's going on inside a person's head-by condensing fact from the vapor of
nuance.
Juanita refused to analyze this process, insisted that it was something
ineffable, something you couldn't explain with words. A radical, rosary-toting
Catholic, she has no problem with that kind of thing. But the bitheads didn't
like it. Said it was irrational mysticism. So she quit and took a job with
some Nipponese company. They don't have any problem with irrational mysticism
as long as it makes money.
But Juanita never comes to The Black Sun anymore. Partly, she's pissed at Da5id
and the other hackers who never appreciated her work. But she has also decided
that the whole thing is bogus. That no matter how good it is, the Metaverse is
distorting the way people talk to each other, and she wants no such distortion
in her relationships. ~ Neal Stephenson,

IN CHAPTERS [0/0]









WORDNET














IN WEBGEN [10000/31]

Wikipedia - 2600: The Hacker Quarterly -- American underground technology publication
Wikipedia - Frank Sinatra (Miss Kittin & The Hacker song) -- 2000 single by Miss Kittin & The Hacker
Wikipedia - Operation Leakspin -- Project coordinated by the hacker group Anonymous
Wikipedia - The Beach (song) -- song by Miss Kittin & The Hacker
Wikipedia - The Hacker and the Ants -- Novel by Rudy Rucker
Wikipedia - The Hackers Conference
https://www.goodreads.com/book/show/2052871.The_Hacker_Ethic
https://www.goodreads.com/book/show/274053.The_Hacker_and_the_Ants
https://www.goodreads.com/book/show/369881.The_Hacker_Ethic
https://www.goodreads.com/book/show/61182.The_Hacker_Crackdown
https://www.goodreads.com/book/show/8969552-the-hacker-ethic
Tron(1982) - Computer Classic, one of the first computer generated movies. A hacker is split into molecules and is transported into a computer. In this computer a mean program called Master Control behaves like a dictator. The hacker, who programmed a number of features of the environment he got into, teams up w...
The Double O Kid(1992) - Lance, a teenager, dreams to be a secret agent when he is suddenly in the middle of an hacker intrigue which aims at an international environmental congress. Lance gets in possession of a computer access card one of which the hackers are in urgent need of for their operation. Lance begins to play wi...
Cyberbully (2015) ::: 6.8/10 -- 1h 2min | Crime, Drama, Mystery | TV Movie 15 January 2015 -- A British teenager is forced by a computer hacker to do his bidding. If she refuses, the hacker will leak compromising photos of her to the public. Director: Ben Chanan Writers: Ben Chanan, David Lobatto Stars:
https://characters.fandom.com/wiki/The_Hacker
.hack//Unison -- -- Bee Train -- 1 ep -- Original -- Adventure Comedy Fantasy Game Magic Sci-Fi -- .hack//Unison .hack//Unison -- Somewhere in the MMORPG called "The World," a group is gathered at a pub, awaiting the start of an event. There, old friends and acquaintances are reunited, including those who rarely log on. Some are even forging new relationships for the first time. Together, invited by the hacker Helba, the group leaves for the event in the Net Slums where a celebration awaits them all. -- -- -- Licensor: -- Bandai Entertainment -- Special - Oct 24, 2003 -- 21,591 6.68
.hack//Unison -- -- Bee Train -- 1 ep -- Original -- Adventure Comedy Fantasy Game Magic Sci-Fi -- .hack//Unison .hack//Unison -- Somewhere in the MMORPG called "The World," a group is gathered at a pub, awaiting the start of an event. There, old friends and acquaintances are reunited, including those who rarely log on. Some are even forging new relationships for the first time. Together, invited by the hacker Helba, the group leaves for the event in the Net Slums where a celebration awaits them all. -- -- Special - Oct 24, 2003 -- 21,591 6.68
Koukaku Kidoutai: Stand Alone Complex -- -- Production I.G -- 26 eps -- Manga -- Action Military Sci-Fi Police Mecha Seinen -- Koukaku Kidoutai: Stand Alone Complex Koukaku Kidoutai: Stand Alone Complex -- In the not so distant future, mankind has advanced to a state where complete body transplants from flesh to machine is possible. This allows for great increases in both physical and cybernetic prowess and blurring the lines between the two worlds. However, criminals can also make full use of such technology, leading to new and sometimes, very dangerous crimes. In response to such innovative new methods, the Japanese Government has established Section 9, an independently operating police unit which deals with such highly sensitive crimes. -- -- Led by Daisuke Aramaki and Motoko Kusanagi, Section 9 deals with such crimes over the entire social spectrum, usually with success. However, when faced with a new A level hacker nicknamed "The Laughing Man," the team is thrown into a dangerous cat and mouse game, following the hacker's trail as it leaves its mark on Japan. -- -- -- Licensor: -- Bandai Entertainment, Manga Entertainment -- TV - Oct 1, 2002 -- 332,809 8.44
Rakuen Tsuihou -- -- Graphinica -- 1 ep -- Original -- Action Sci-Fi Mecha -- Rakuen Tsuihou Rakuen Tsuihou -- In a future where a massive disaster has devastated Earth, most of humanity has abandoned their physical bodies and relocated in digital form to DEVA, an advanced space station orbiting the ravaged planet. Free from the limitations of traditional existence, such as death and hunger, the inhabitants of this virtual reality reside in relative peace until Frontier Setter, a skilled hacker, infiltrates the system and spreads subversive messages to the populace. -- -- Labeled a threat to security by authorities, Frontier Setter is pursued by Angela Balzac, a dedicated member of DEVA's law enforcement. When the hacker's signal is traced to Earth, Angela takes on physical form, transferring her consciousness to a clone body and traveling to the world below in order to deal with the menace. On Earth, she is assisted by Dingo, a charismatic agent, and during her journey to uncover the mystery behind Frontier Setter, she gradually discovers startling realities about the wasteland some of humanity still refers to as home, as well as the paradise above. -- -- -- Licensor: -- Aniplex of America -- Movie - Nov 15, 2014 -- 83,758 7.37
Rakuen Tsuihou -- -- Graphinica -- 1 ep -- Original -- Action Sci-Fi Mecha -- Rakuen Tsuihou Rakuen Tsuihou -- In a future where a massive disaster has devastated Earth, most of humanity has abandoned their physical bodies and relocated in digital form to DEVA, an advanced space station orbiting the ravaged planet. Free from the limitations of traditional existence, such as death and hunger, the inhabitants of this virtual reality reside in relative peace until Frontier Setter, a skilled hacker, infiltrates the system and spreads subversive messages to the populace. -- -- Labeled a threat to security by authorities, Frontier Setter is pursued by Angela Balzac, a dedicated member of DEVA's law enforcement. When the hacker's signal is traced to Earth, Angela takes on physical form, transferring her consciousness to a clone body and traveling to the world below in order to deal with the menace. On Earth, she is assisted by Dingo, a charismatic agent, and during her journey to uncover the mystery behind Frontier Setter, she gradually discovers startling realities about the wasteland some of humanity still refers to as home, as well as the paradise above. -- -- Movie - Nov 15, 2014 -- 83,758 7.37
The Animatrix -- -- Madhouse, Studio 4°C -- 9 eps -- Other -- Action Drama Sci-Fi -- The Animatrix The Animatrix -- 1. Final Flight of the Osiris -- The crew of the Osiris discover an army preparing to invade Zion. While one crew member races inside the Matrix to get the message to Zion, the others try desperately to buy her enough time while fighting off an onslaught of Sentinels they can't possibly defeat. -- -- 2-3. The Second Renaissance Part 1 and 2 -- Humans have created the ultimate AI, which is just as smart as they are. But complications arise when these robots and the humans try to exist peacefully, and eventually all-out war breaks out. The humans ultimately lose the war, and become trapped in the Matrix as seen in the live-action films. -- -- 4. Kid's Story -- A young man discovers that his world isn't real, that it's a computer-generated fantasy land created by robots using humans for energy. He escapes with the help of the hacker Neo. Based on the Matrix trilogy. -- -- 5. Program -- Cis and Duo engage in battle in a virtual recreation of Feudal Japan. -- -- 6. World Record -- While running the fastest race in his life, a champion track star breaks free of his computer-generated world for a small period of time. When he goes back to the real world, he has no memories and is placed in a nursing home. Based on the Matrix trilogy. -- -- 7. Beyond -- While looking for her lost pet, a young woman meets up with some kids in Tokyo to play in a "haunted house," which is really a glitch in their computer world. Based on the Matrix trilogy. -- -- 8. Detective Story -- A detective named Ash is called upon by a mysterious organization to hunt down the notorious hacker Trinity. -- -- 9. Matriculated -- A group of scientists capture a robot and place it in a surreal fantasy world. When the robot's friends come in and kill most of the scientists; however, the robot and the last scientist remaining face isolation in the computer-generated world. Based on the Matrix trilogy. -- -- (Source: ANN) -- -- Licensor: -- Warner Bros. Japan -- OVA - Jun 3, 2003 -- 66,027 7.30
The Animatrix -- -- Madhouse, Studio 4°C -- 9 eps -- Other -- Action Drama Sci-Fi -- The Animatrix The Animatrix -- 1. Final Flight of the Osiris -- The crew of the Osiris discover an army preparing to invade Zion. While one crew member races inside the Matrix to get the message to Zion, the others try desperately to buy her enough time while fighting off an onslaught of Sentinels they can't possibly defeat. -- -- 2-3. The Second Renaissance Part 1 and 2 -- Humans have created the ultimate AI, which is just as smart as they are. But complications arise when these robots and the humans try to exist peacefully, and eventually all-out war breaks out. The humans ultimately lose the war, and become trapped in the Matrix as seen in the live-action films. -- -- 4. Kid's Story -- A young man discovers that his world isn't real, that it's a computer-generated fantasy land created by robots using humans for energy. He escapes with the help of the hacker Neo. Based on the Matrix trilogy. -- -- 5. Program -- Cis and Duo engage in battle in a virtual recreation of Feudal Japan. -- -- 6. World Record -- While running the fastest race in his life, a champion track star breaks free of his computer-generated world for a small period of time. When he goes back to the real world, he has no memories and is placed in a nursing home. Based on the Matrix trilogy. -- -- 7. Beyond -- While looking for her lost pet, a young woman meets up with some kids in Tokyo to play in a "haunted house," which is really a glitch in their computer world. Based on the Matrix trilogy. -- -- 8. Detective Story -- A detective named Ash is called upon by a mysterious organization to hunt down the notorious hacker Trinity. -- -- 9. Matriculated -- A group of scientists capture a robot and place it in a surreal fantasy world. When the robot's friends come in and kill most of the scientists; however, the robot and the last scientist remaining face isolation in the computer-generated world. Based on the Matrix trilogy. -- -- (Source: ANN) -- OVA - Jun 3, 2003 -- 66,027 7.30
2600: The Hacker Quarterly
In the Realm of the Hackers
The Hacker's Diet
The Hacker's Handbook
The Hacker Crackdown
The Hacker Ethic
The Hacker Files
The Hackers Conference
The Hacker Wars



convenience portal:
recent: Section Maps - index table - favorites
Savitri -- Savitri extended toc
Savitri Section Map -- 1 2 3 4 5 6 7 8 9 10 11 12
authors -- Crowley - Peterson - Borges - Wilber - Teresa - Aurobindo - Ramakrishna - Maharshi - Mother
places -- Garden - Inf. Art Gallery - Inf. Building - Inf. Library - Labyrinth - Library - School - Temple - Tower - Tower of MEM
powers -- Aspiration - Beauty - Concentration - Effort - Faith - Force - Grace - inspiration - Presence - Purity - Sincerity - surrender
difficulties -- cowardice - depres. - distract. - distress - dryness - evil - fear - forget - habits - impulse - incapacity - irritation - lost - mistakes - obscur. - problem - resist - sadness - self-deception - shame - sin - suffering
practices -- Lucid Dreaming - meditation - project - programming - Prayer - read Savitri - study
subjects -- CS - Cybernetics - Game Dev - Integral Theory - Integral Yoga - Kabbalah - Language - Philosophy - Poetry - Zen
6.01 books -- KC - ABA - Null - Savitri - SA O TAOC - SICP - The Gospel of SRK - TIC - The Library of Babel - TLD - TSOY - TTYODAS - TSZ - WOTM II
8 unsorted / add here -- Always - Everyday - Verbs


change css options:
change font "color":
change "background-color":
change "font-family":
change "padding":
change "table font size":
last updated: 2022-05-05 17:16:27
325548 site hits