Related:

• OS/2: /O S too/ n. The anointed successor to MS-DOS for Intel 286- and 386-based micro
  proof that IBM/Microsoft couldn't get it right the second time, either....
• MS-DOS:: /M-S-dos/ [MicroSoft Disk Operating System] n.
  A {clone} of {{CP/M}} for the 8088 crufted together in 6 weeks by hacker Tim Paterson, who is said to have regretted it ever since....
• interrupt: 1. [techspeak] n. On a computer, an event that interrupts normal processing and temporarily diverts flow-of-control through an "interrupt handler" routine.
  See also {trap}. 2. interj. A request for attention from a hacker....
• MS-DOS /M-S-dos/ n. [MicroSoft Disk Operating System] A clone of CP/M for the 8088 crufted together in 6 weeks by hacker Tim Paterson at Seattle Computer Produc
  who called the original QDOS (Quick and Dirty Operating System) and is said to have regretted it ever since....
• DEC /dek/ n. 1. v. Verbal (and only rarely written) shorthand for decrement, i.
  e. `decrease by one'. Especially used by assembly programmers, as many assembly languages have a dec mnemonic....
• DEC: n. Digital Equipment Corporation. Before the {killer micro} revolution of the late 1980s, hackerdom was closely symbiotic with DEC's pioneering timesharing machines.
  The first of the group of cultures described by this lexicon nucleated around the PDP-1 (see {TMRC}....
• Microsloth Windows: /mi:'kroh-sloth` win'dohz/ n. Hackerism for `Microsoft Windows'
  a windowing system for the IBM-PC which is so limited by bug-for-bug compatibility with {mess-dos} that it is agonizingly slow on anything less than a fast 486....
• econd-system effect: n. (sometimes, more euphoniously
  `second-system syndrome') When one is designing the successor to a relatively small, elegant, and successful system, there is a tendency to become grandiose in one's success and design an {elephantine} feature-laden monstrosity....
• Brooks's Law: prov. "Adding manpower to a late software project makes it later" -- a result of the fact that the expected advantage from splitting work among N programmers is O(N) (that i
  proportional to N), but the complexity and communications cost associated with coordinating and then merging their work is O(N^2) (that is, proportional to the square of N)....