Related:

• Overall, the philosophy is to attack the availability problem from two complementary directio
  o reduce the number of software errors through rigorous testing of running systems, and to reduce the effect of the remaining errors by providing for recovery from them....
• The subtlety of these methods implies an important source of unreliability
  unreliable error recovery. Thus it is important that system testing pay meticulous attention to fault simulation to uncover weaknesses in the recovery....
• footprint n. 1. The floor or desk area taken up by a piece of hardware.
  2. [IBM] The audit trail (if any) left by a crashed program (often in plural, `footprints')....
• 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....
• 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....
• patch 1. n. A temporary addition to a piece of code, usually as a quick-and-dirty remedy to an existing bug or misfeature.
  A patch may or may not work, and may or may not eventually be incorporated permanently into the program....
• beta /bay't*/, /be't*/ or (Commonwealth) /bee't*/ n.
  1. Mostly working, but still under test; usu. used with `in'...
• MFTL /M-F-T-L/ [abbreviation: `My Favorite Toy Language'] 1.
  adj. Describes a talk on a programming language design that is heavy on the syntax (with lots of BNF), sometimes even talks about semantics (e....
• 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....