Halt and Catch Fire and ancient computer culture

Spending too many hours staring at ancient assembly language (SEL/Gould Macro Assembler for the 32/87, running under MPX-32) brought to mind an old bit of often-mimeographed humor which may date back to the 1970s, if not earlier: A list of fictitious assembly language instructions, including

HCF (HALT AND CATCH FIRE)
BOB (BRANCH ON BUG)
FLI (FLASH LIGHTS IMPRESSIVELY)
JTZ (JUMP TO TWILIGHT ZONE)
KCE (KILL CONSULTANT ON ERROR)
LAP (LAUGH AT PROGRAMMER)
LPA (LEAD PROGRAMMER ASTRAY)

And here's another trip down random-access memory lane: The Jargon File version 3.1.0. Born in 1975 at Stanford, this collection of computer geek jargon made its way by FTP across the nascent ARPAnet to the MIT AI Lab, went dormant in the mid- to late-80s, then was reborn in 1990 and gave birth to a book version (The New Hacker's Dictionary). The linked version is from October 1994, but here's a version from 2000.

Fellow geeks: What's your favorite ancient bit of tech humor or insider geek culture? Tell us about it in the comments.

[Regarding assembly language, for you non-programmers: Imagine having to describe a simple act, like turning a door knob, as a series of commands to each individual muscle in your fingers, hand, arm, and shoulder. A simple action on your computer is accomplished by what may be a lengthy and complex series of simple instructions to the machine's brain -- the central processing unit (CPU). Those simple instructions are represented in somewhat human-readable terms by mnemonics. Programmers would have to know these mnemonics to write a computer program. Another program, called an assembler, would turn these arcane mnemonics into even more incomprehensible 1s and 0s understood by the CPU. Nowadays, programmers use somewhat less arcane computer languages to describe what the computer is supposed to do, and a program called a compiler turns a program written by a human into 1s and 0s for the CPU.]