Gutenberg Articles

Appearance

Excerpt ​

Excerpt from The Jargon File, Version 4.0.0, 24 Jul 1996, by Unknown Author

:ABEND: /a'bend/, /*-bend'/ /n./ [ABnormal END] Abnormal
termination (of software); {crash}; {lossage}. Derives from
an error message on the IBM 360; used jokingly by hackers but
seriously mainly by {code grinder}s. Usually capitalized, but
may appear as abend'. Hackers will try to persuade you that<br /> ABEND is called abend' because it is what system operators do to
the machine late on Friday when they want to call it a day, and
hence is from the German Abend' = Evening'.

:accumulator: /n. obs./ 1. Archaic term for a register. On-line
use of it as a synonym for register' is a fairly reliable<br /> indication that the user has been around for quite a while and/or<br /> that the architecture under discussion is quite old. The term in<br /> full is almost never used of microprocessor registers, for example,<br /> though symbolic names for arithmetic registers beginning in A'
derive from historical use of the term accumulator' (and not,<br /> actually, from arithmetic'). Confusingly, though, an A'<br /> register name prefix may also stand for address', as for
example on the Motorola 680x0 family. 2. A register being used for
arithmetic or logic (as opposed to addressing or a loop index),
especially one being used to accumulate a sum or count of many
items. This use is in context of a particular routine or stretch
of code. "The FOOBAZ routine uses A3 as an accumulator."
3. One's in-basket (esp. among old-timers who might use sense 1).
"You want this reviewed? Sure, just put it in the accumulator."
(See {stack}.)

:ACK: /ak/ /interj./ 1. [from the ASCII mnemonic for 0000110]
Acknowledge. Used to register one's presence (compare mainstream
Yo!). An appropriate response to {ping} or {ENQ}.
2. [from the comic strip "Bloom County"] An exclamation of
surprised disgust, esp. in "Ack pffft!" Semi-humorous.
Generally this sense is not spelled in caps (ACK) and is
distinguished by a following exclamation point. 3. Used to
politely interrupt someone to tell them you understand their point
(see {NAK}). Thus, for example, you might cut off an overly
long explanation with "Ack. Ack. Ack. I get it now".

Explanation ​

This excerpt is from The Jargon File (also known as The New Hacker’s Dictionary), a famous compendium of hacker slang, programming lore, and computing subculture terminology. First compiled in the 1970s and updated over decades, the file documents the informal language of programmers, system administrators, and early computer enthusiasts. The entries blend technical definitions with humor, historical anecdotes, and cultural references, reflecting the playful yet precise communication style of hacker culture.

Below is a detailed breakdown of the three entries (ABEND, accumulator, and ACK), focusing on their textual content, linguistic features, themes, and significance within hacker culture.

1. ABEND ​

Text:

:ABEND: /a'bend/, /*-bend'/ /n./ [ABnormal END] Abnormal termination (of software); {crash}; {lossage}. Derives from an error message on the IBM 360; used jokingly by hackers but seriously mainly by {code grinder}s. Usually capitalized, but may appear as abend'. Hackers will try to persuade you that ABEND is called abend' because it is what system operators do to the machine late on Friday when they want to call it a day, and hence is from the German Abend' = Evening'.

Explanation & Analysis: ​

  • Definition & Origin:

    • ABEND stands for "ABnormal END", a term for a software crash or unexpected termination. It originates from IBM 360 mainframe error messages, where it was a formal diagnostic term.
    • The entry notes that while code grinders (uninspired, grind-it-out programmers) use it seriously, hackers (skilled, creative programmers) use it jokingly, reflecting a cultural divide between "serious" corporate computing and the more playful hacker ethos.

  • Linguistic Play & Humor:

    • The entry includes a folk etymology—a humorous, false origin story—that ABEND comes from the German Abend ("evening"), implying that sysadmins "end" (shut down) systems on Friday evenings. This is a classic example of hacker humor:
      • It subverts technical jargon by giving it a whimsical, human-scale meaning.
      • It mockingly anthropomorphizes machines, framing crashes as something operators choose to do (like leaving work early).
      • The joke also pokes at corporate culture, where rigid schedules (e.g., "Friday evening") contrast with the hacker’s 24/7, problem-solving mindset.

  • Capitalization & Variation:

    • The entry notes that ABEND is usually capitalized (as an acronym) but may appear as abend, showing how technical terms evolve in informal usage.

  • Themes:

    • Technical vs. Cultural Meaning: The tension between the term’s literal origin (IBM error codes) and its cultural repurposing (as a joke) highlights how hackers reclaim and reshape language.
    • Humor as Coping Mechanism: Crashes are frustrating, so humor (e.g., the German Abend story) serves as a way to diffuse stress in high-pressure technical work.

2. accumulator ​

Text:

:accumulator: /n. obs./ 1. Archaic term for a register. On-line use of it as a synonym for register' is a fairly reliable indication that the user has been around for quite a while and/or that the architecture under discussion is quite old. The term in full is almost never used of microprocessor registers, for example, though symbolic names for arithmetic registers beginning in A' derive from historical use of the term accumulator' (and not, actually, from arithmetic'). Confusingly, though, an A' register name prefix may also stand for address', as for example on the Motorola 680x0 family. 2. A register being used for arithmetic or logic (as opposed to addressing or a loop index), especially one being used to accumulate a sum or count of many items. This use is in context of a particular routine or stretch of code. "The FOOBAZ routine uses A3 as an accumulator." 3. One's in-basket (esp. among old-timers who might use sense 1). "You want this reviewed? Sure, just put it in the accumulator." (See {stack}.)

Explanation & Analysis: ​

  • Definition & Historical Context:

    • An accumulator is an archaic term for a CPU register, specifically one used for arithmetic operations. The entry marks it as "obs." (obsolete), signaling its decline in modern usage.
    • Its persistence in older architectures (e.g., early mainframes) or in register names starting with 'A' (e.g., A0, A1) reveals how historical terminology lingers in computing, even as technology evolves.

  • Three Meanings:

    1. Literal (Hardware):
      • A register in old systems (e.g., 1950s–60s computers) dedicated to arithmetic. The entry notes that while the full term is rare in microprocessors, the 'A' prefix (e.g., A3) often hints at this legacy.
      • The confusion with 'address' registers (also sometimes labeled 'A') shows how naming conventions collide across architectures.
    2. Contextual (Software):
      • In code, an accumulator can refer to any register temporarily holding a running total (e.g., summing values in a loop). This is a functional rather than structural definition.
      • Example: "The FOOBAZ routine uses A3 as an accumulator." → Here, A3 isn’t inherently an "accumulator register"; it’s repurposed for accumulation in this specific routine.
    3. Metaphorical (Office Humor):
      • Playfully extends the term to mean an in-basket (where tasks "accumulate"). This is a metaphorical leap from hardware to office life, showing how hackers apply technical metaphors to everyday contexts.
      • The parenthetical "(esp. among old-timers)" ties this usage to veteran programmers, reinforcing the term’s nostalgic, insider status.

  • Linguistic Features:

    • Technical Precision: The entry carefully distinguishes between historical hardware accumulators and contextual software usage, showing how terms shift meaning over time.
    • Humor & Insider Knowledge: The in-basket joke assumes familiarity with both registers and office culture, rewarding those "in the know."
    • Cross-Reference: The note "(See {stack})" links to another term, encouraging readers to explore related concepts—a common feature in The Jargon File.

  • Themes:

    • Evolution of Language: The entry traces how a hardware-specific term becomes generalized (software) and then metaphorical (in-basket), reflecting how technical jargon adapts and persists.
    • Generational Knowledge: The term’s obsolescence marks the user as an "old-timer," creating a hierarchy of expertise within hacker culture.
    • Playful Repurposing: The in-basket meaning shows how hackers reuse technical terms for humor, blending work and play.

3. ACK ​

Text:

:ACK: /ak/ /interj./ 1. [from the ASCII mnemonic for 0000110] Acknowledge. Used to register one's presence (compare mainstream Yo!). An appropriate response to {ping} or {ENQ}. 2. [from the comic strip "Bloom County"] An exclamation of surprised disgust, esp. in "Ack pffft!" Semi-humorous. Generally this sense is not spelled in caps (ACK) and is distinguished by a following exclamation point. 3. Used to politely interrupt someone to tell them you understand their point (see {NAK}). Thus, for example, you might cut off an overly long explanation with "Ack. Ack. Ack. I get it now".

Explanation & Analysis: ​

  • Definition & Origins:

    • ACK is short for "Acknowledge," derived from the ASCII control character (0000110, used in data transmission to confirm receipt).
    • The entry highlights its three distinct uses, each with different tones and contexts.

  • Three Meanings:

    1. Technical (Networking):
      • A response to {ping} or {ENQ} (other control signals), mirroring its role in data protocols. This is the most literal use, tied to low-level computing.
      • The comparison to "Yo!" frames it as a casual, human-like greeting in machine communication.
    2. Pop Culture (Comic Strip):
      • Borrowed from Bloom County (a 1980s satirical comic), where "Ack pffft!" expresses disgust or frustration. This is purely humorous and non-technical.
      • The entry notes it’s not capitalized in this sense and often followed by an exclamation point, showing how context distinguishes meanings.
    3. Social (Conversation):
      • A polite interruption to signal understanding (e.g., "Ack. Ack. Ack. I get it now"). This is metacommunicative—it’s about managing conversation flow.
      • The reference to {NAK} ("Negative Acknowledge") suggests a binary pair: ACK (understood) vs. NAK (not understood).

  • Linguistic Features:

    • Homophony & Polysemy: The same sound (/ak/) has multiple unrelated meanings, requiring context to disambiguate.
    • Cultural Blending: The term moves from technical protocols to comics to social interaction, showing how hacker slang absorbs external influences.
    • Tone Shifts: The meanings range from serious (networking) to silly (comics) to practical (conversation), reflecting the versatility of hacker language.

  • Themes:

    • Adaptation of Technical Terms: ACK starts as a machine signal but becomes a human utterance, illustrating how technology shapes language.
    • Humor as Glue: The Bloom County reference shows how pop culture infiltrates technical communities, adding levity.
    • Efficiency in Communication: Using ACK to interrupt politely reflects hackers’ value for concise, clear interaction—even in speech.

Broader Significance of the Excerpt ​

  1. Language as a Cultural Artifact:

    • The entries show how hacker slang is both precise and playful, blending technical accuracy with humor, history, and metaphor.
    • Terms like ABEND and accumulator carry generational knowledge, marking insiders vs. outsiders.

  2. Humor and Coping:

    • Jokes (e.g., ABEND’s German origin, accumulator as an in-basket) humanize technology, making abstract concepts relatable and fun.
    • This reflects a hacker ethos that values creativity and resilience in the face of frustrating systems.

  3. Evolution of Meaning:

    • Words shift from literal to metaphorical (e.g., accumulator), showing how language adapts as technology changes.
    • The obsolescence of terms (e.g., "accumulator") also highlights the rapid pace of computing history.

  4. Community and Identity:

    • Knowing these terms signals membership in hacker culture. The inside jokes and historical references create a shared identity.
    • The contrasts (e.g., hackers vs. code grinders, old-timers vs. newcomers) reinforce hierarchies of expertise.

  5. Bridge Between Human and Machine:

    • Terms like ACK and ABEND anthropomorphize machines, while metaphors (accumulator as in-basket) technologize human experiences.
    • This blurring of boundaries is central to hacker culture, where people and computers are collaborators.

Conclusion ​

This excerpt from The Jargon File is more than a dictionary—it’s a cultural snapshot of hacker communication. The entries define terms while also telling stories, making jokes, and preserving history. They reveal a community that values precision but also play, respects tradition but embraces change, and finds humor in the gaps between humans and machines. By studying these definitions, we see how language shapes (and is shaped by) technology, humor, and identity.