Related:

• bit n. [from the mainstream meaning and `Binary digIT'] 1.
  [techspeak] The unit of information; the amount of information obtained by asking a yes-or-no question for which the two outcomes are equally probable....
• bit-paired keyboard n.,obs. (alt. `bit-shift keyboard') A non-standard keyboard layout that seems to have originated with the Teletype ASR-33 and remained common for several years on early computer equipment.
  The ASR-33 was a mechanical device (see EOU), so the only way to generate the character codes from keystrokes was by some physical linkage....
• bit bucket n. [very common] 1. The universal data sink (originally, the mythical receptacle used to catch bits when they fall off the end of a register during a shift instruction).
  Discarded, lost, or destroyed data is said to have `gone to the bit bucket'....
• o-op /noh'op/ n.,v. alt. NOP /nop/ [no operation] 1.
  A machine instruction that does nothing (sometimes used in assembler-level programming as filler for data or patch areas, or to overwrite code to be removed in binaries)....
• o-op: /noh'op/ alt. NOP /nop/ [no operation] n. 1.
  (also v.) A machine instruction that does nothing (sometimes used in assembler-level programming as filler for data or patch areas, or to overwrite code to be removed in binaries)....
• This modem will now self destruct...5..4..3..2..1..0..
• one-liner wars n. A game popular among hackers who code in the language APL (see write-only language and line noi and/or useful routine in one line of operators chosen from APL's exceedingly hairy primitive set.
  A similar amusement was practiced among TECO hackers and is now popular among Perl aficionados....
• one-liner wars: n. A game popular among hackers who code in the language APL (see {write-only language} and {line noise}).
  The objective is to see who can code the most interesting and/or useful routine in one line of operators chosen from APL's exceedingly {hairy} primitive set....
• hot spot: n. 1. [primarily used by C/UNIX programmers, but spreading] It is received wisdom that in most programs, less than 10% of the code eats 90% of the execution time
  if one were to graph instruction visits versus code addresses, one would typically see a few huge spikes amidst a lot of low-level noise....