Eric S. Raymond, Guy L. Steele · Project Gutenberg · Analyzed by Maliang Writer
"The Jargon File, Version 4.2.2, 20 Aug 2000" by Eric S. Raymond and Guy L. Steele is a glossary published in 2000. Born from MIT's AI Lab and early hacker communities of the 1950s, this dictionary captures the colorful slang and technical terminology of computer programmers. Through decades of evolution—from handwritten files to published books—it documents a vanishing culture of innovation, bec…
EncyclopediasDictionariesReferenceJournalismMediaWritingComputersHumorSlangElectronic data processing
Chapters30
Words47,338
Characters6
World entries12
Foreshadowing5
Pacing rating5.2/10
Source
Where to read the original
This book is published on Project Gutenberg. Read the full text there.
This page summarizes our analysis of the book. It does not reproduce the text.
Overview
Pacing at a glance
Pacing pattern:Alphabetical march with alternating dense history entries and thin slang entries; the longest and most rewarding entries cluster in Chapters 21, 24 and 29, while transitional and single-entry chapters (22, 28, 30) interrupt the rhythm.
Emotional curve:A slow alphabetical climb with one sharp political peak at the CDA and two comic dips, the node-list index and the code grinder sketch
What works
Chapters 1-10: The text is rich in specific, authentic jargon and cultural detail, effectively immersing the reader in hacker culture.
Chapters 12 and 15 use long quoted artifacts and institutional anecdotes to turn reference entries into comic set pieces, giving readers a reason to keep reading past the short definitions.
Chapter 21 builds the bug entry from a 1947 logbook moth back to Shakespeare, turning a definition into a small detective story.
Where it slows down
Chapters 1-10: There is no narrative, conflict, or character development, making it unsuitable as a novel and highly likely to bore readers seeking story.
Chapters 17 and 20 are dominated by short, abstract, cross-referenced definitions with few anecdotes, so the reading experience sags and momentum is lost.
Chapter 22 is mostly the C node list plus a stub, with no definition to carry the reader, and it is the batch's main dropoff point.
Story arcs
Arc
Chapters
Climax
Lexicon entries
1–30
Ch. 24
Characters
Main characters
Eric S. RaymondSupporting Editor and compiler of the Jargon File lexicon, identified by the initials ESR in editorial notes.
B1FFSupporting Fictional archetype of the clueless newbie poster on Usenet, used as a comic example of netiquette failure.
Edsger W. DijkstraSupporting Frequently quoted authority whose observations on BASIC and COBOL are used as touchstones of hackish opinion.
Ken ThompsonSupporting Co-inventor of Unix whose epigram about brute force is quoted to summarize a design philosophy.
Fred BrooksSupporting Author of The Mythical Man-Month whose law about adding manpower underlies the cathedral model discussion.
Linus TorvaldsSupporting Named as creator of a Linux naming joke and as the figure who apologized after an early release bug.
World
World-building and key terms
metasyntactic variableOther Placeholder names like foo, bar and baz used in examples, with regional variants such as fred and barney. Their ordering is conventional rather than arbitrary.
UsenetFaction The distributed discussion network whose conventions shape hacker writing: inclusion quoting with > leaders, April Fool's hoaxes, spam and cancelbots, and a pr…
The Jargon FileWorld A living lexicon documenting hacker slang, described as a body of usage that evolved across ARPANET, Usenet, MUDs and academic labs and that mixes humour, tech…
hackishOther The composite dialect of hacker speech and writing, including spoken names for punctuation, verb doubling, and borrowed programming syntax used in ordinary pro…
bazaarPower system Development model observed in the Linux community: release early and often and recruit the widest possible pool of reviewers. Contrasts with the small-team cat…
Brooks's LawOther Project-management principle that adding manpower to a late software project makes it later, because coordination costs grow with the square of the number of p…
inclusion conventionOther Rules for marking quoted material in email and netnews: indentation with a leading >, nesting by repeated leaders, deletion of irrelevant lines, and disapprova…
cathedralOther Classical software-engineering style: small teams, tight central control and long release intervals, long assumed necessary because of Brooks's Law.
BSDFaction A family of Unix variants developed at Berkeley from the late 1970s, including paged virtual memory and TCP/IP networking, whose descendants remain widely used.
bogonOther The notional elementary particle of bogosity; also used for malformed packets and, by extension, bogus people or things. A whole family of joke particles has g…
Blue Screen of DeathOther The fatal error screen displayed when Microsoft Windows crashes, often decorated with hex codes; commonly abbreviated BSOD and treated as the archetypal system…
blinkenlightsItem Front-panel diagnostic lamps on a computer, and later status lights on modems, hubs and networking equipment; a revival in usage on network gear is noted.
Foreshadowing
Foreshadowing and open threads
B1FF's hidden creatorReinforced The editor hints that B1FF was originally created by Joe Talmadge and passed to Richard Sexton, suggesting the persona has an authored history behind its appar…
The cathedral and the bazaarOpen The bazaar entry alludes to an analytical paper about development models and says Brooks's Law is not the whole story, pointing toward a larger argument about …
Cokebottle's second inningOpen The cokebottle entry observes the term may be due for a revival, hinting at a return of unusual keystroke terminology as Motif and similar systems use strange …
CDA and White ThursdayReinforced The CDA entry describes a protest movement and a court ruling that struck the law down, leaving an open thread about free-speech battles over networks.
Cancelmoose's retirementReinforced Cancelmoose is described as having stepped back from spam cancelling to pursue ending spam entirely, raising the question of how spam will be dealt with later.
Pacing
Highest-scoring chapters
Every analyzed chapter (30 in total) is scored for tension, information density, emotional intensity and conflict. These are the 15 chapters with the highest overall score.
Ch. 241. A huge volume of spurious error-message output produced by · tension 6.7 Climax The lexicon continues through C. Cascade is defined as compiler error spam or a chain of Usenet followups; case and paste and clone-and-hack coding describe copying features; casting the runes tells …
Ch. 233. The name of a programming language designed by Dennis Ritchie · tension 3.4 Buildup The C entries proper begin. C is defined as Dennis Ritchie's early-1970s language, reimplementing Unix and named after B. C Programmer's Disease describes fixed table sizes and recompilation. C++ is …
Ch. 141. Informal name for one of the four standard references on · tension 5.3 Buildup Blue Book is defined three ways: a PostScript reference, a Smalltalk reference, and the 1988 CCITT standards including X.400 and the fax groups. The text then turns to blue box, the obsolete phreakin…
Ch. 151. In-context synonym for bboard; · tension 3 Buildup Board is given two senses, a synonym for bboard and an electronic circuit board, before the chapter moves through boat anchor, bob, bodysurf code, BOF, BOFH, bogo-sort, bogometer, BogoMIPS, bogon, bo…
Ch. 201. Debugging statements inserted into a program that emit · tension 3 Buildup Bread crumbs are defined as debugging statements inserted into a program to show where it dies, traced to Hansel and Gretel and Thumbelina, and, in user-interface design, as features that track where…
Ch. 211. Not working properly (of programs). 2. Behaving strangely; · tension 2.3 Buildup The lexicon moves through the B entries from broken and broken arrow to busy-wait and buzz. It defines broken arrow as an IBM 3270 error code and notes its military sense; gives Brooks's Law with its…
Ch. 291. A person only capable of grinding out code, but unable to · tension 3.4 Buildup code monkey is defined in three senses: a grinder incapable of design, any programmer, and a self-deprecating denial of responsibility for management decisions. code police invokes Orwell's thought p…
Ch. 301. One who eats (computer) bugs for a living. One who fulfills · tension 4.5 Transition computer geek is defined in two senses: the asocial, malodorous monomaniac of the negative stereotype, and the positive self-description that grew after 1990, with the outsider/insider asymmetry comp…
Ch. 121. Syn. blast, sense 1. 2. See · tension 3 Buildup The entry continues the definition of blat as a synonym for blast and a pointer to thud, then proceeds through bletch, bletcherous, blink, blinkenlights, blit, blitter and into blivet. Bletcherous is…
Ch. 181. An Internet user that leeches off ISPs - the sort you can · tension 1 Buildup Bottom feeder is defined as an Internet user who leeches off ISPs, always complains about price, and is known for spam and flamage; a second sense links it to slopsucker. The chapter then moves throu…
Ch. 191. A computer; esp. in the construction `foo box' where · tension 1 Buildup Box is defined as a computer, especially in constructions like 'Unix box', and, within an SNA site, as an IBM front-end processor, with the cry that goes up when the box has fallen over. The chapter …
Ch. 41. Something, such as a program or a computer, that fails to · tension 6.4 Transition The text defines terms including 'bagbiter' (a failing program or person), 'baggy pantsing' (a prank for unlocked terminals), 'bamf' (a teleportation sound), 'bandwidth' (attention span), and 'bang p…
Ch. 81. One of a small number of fundamental source books such as · tension 1 Transition The text defines terms including 'BiCapitalization', 'B1FF' (a prototypical newbie), 'biff' (to notify of mail), 'Big Gray Wall' (VMS documentation), and 'big-endian' (byte order). Each entry gives p…
Ch. 261. An exact duplicate: "Our product is a clone of their · tension 2.3 Buildup The clone entry is completed in six senses, from exact duplicate and shoddy copy to legal ripoff, PC clone and Unix clone, plus the verb. clone-and-hack coding is referred back to case and paste; clo…
Ch. 271. Unuseable CD produced during failed attempt at writing to · tension 2.3 Pressure coaster is finished, including the British beermat variant. COBOL is then defined as a weak, verbose language, with Dijkstra's remark that teaching it should be a criminal offense. COBOL fingers desc…
Contents
Chapter list
C. Despite this, it was favored 3:1 over ** in a late-1990
1. Archaic term for a register. On-line use of it as a synonym
1. In a regular expression or pattern match, the text which
1. Something, such as a program or a computer, that fails to
1. The title page added to printouts by most print spoolers
1. Non-interactive. Hackers use this somewhat more loosely
1. Mostly working, but still under test; usu. used with `in'
1. One of a small number of fundamental source books such as
2. Synonym for blit or BLT. Both uses are borderline techspeak
1. Information. Examples: "I need some bits about file
1. A computer sufficiently small, primitive, or incapable as
1. Syn. blast, sense 1. 2. See
2. A crucial piece of hardware that can't be fixed or replaced if
1. Informal name for one of the four standard references on
1. In-context synonym for bboard;
4. Incorrect. "That algorithm is bogus." 5. Unbelievable. "You
2. An AI-controlled player in a computer game (especially a
1. An Internet user that leeches off ISPs - the sort you can
1. A computer; esp. in the construction `foo box' where
1. Debugging statements inserted into a program that emit
1. Not working properly (of programs). 2. Behaving strangely;
1. Of a program, to run with no indication of progress and
3. The name of a programming language designed by Dennis Ritchie
1. A huge volume of spurious error-message output produced by
1. To lose; specifically, to chew
1. An exact duplicate: "Our product is a clone of their
1. Unuseable CD produced during failed attempt at writing to
1. A suit-wearing minion of the
1. A person only capable of grinding out code, but unable to
1. One who eats (computer) bugs for a living. One who fulfills
FAQ
Frequently asked questions
What is The Jargon File, Version 4.2.2, 20 Aug 2000 about?
"The Jargon File, Version 4.2.2, 20 Aug 2000" by Eric S. Raymond and Guy L. Steele is a glossary published in 2000. Born from MIT's AI Lab and early hacker communities of the 1950s, this dictionary captures the colorful slang and technical terminology of computer programmers. Through decades of evo…
How was The Jargon File, Version 4.2.2, 20 Aug 2000 analyzed?
Maliang Writer's analysis agents read the book chapter by chapter. They scored 30 chapters for pacing and recorded 6 character profiles and 12 world-building entries. The results are generated automatically and cross-checked.
Where can I read The Jargon File, Version 4.2.2, 20 Aug 2000?
The original is published on Project Gutenberg; the link is in the Source section of this page.
Does this page contain the text of the book?
No. It only shows structured analysis: character and setting summaries, chapter titles, pacing scores and one-line chapter summaries.
Maliang Writer runs the same agents on the novel you are writing: characters, world-building, foreshadowing and chapter pacing, kept up to date as you write.