Related:

• cray instability: n. A shortcoming of a program or algorithm that manifests itself only when a large problem is being run on a powerful machine (see {cray}).
  Generally more subtle than bugs that can be detected in smaller problems running on a workstation or mini....
• crayon n. 1. Someone who works on Cray supercomputers.
  More specifically, it implies a programmer, probably of the CDC ilk, probably male, and almost certainly wearing a tie (irrespective of gender)....
• HAKMEM /hak'mem/ n. MIT AI Memo 239 (February 1972).
  A legendary collection of neat mathematical and programming hacks contributed by many people at MIT and elsewhere....
• crayon: n. 1. Someone who works on Cray supercomputers.
  More specifically, it implies a programmer, probably of the CDC ilk, probably male, and almost certainly wearing a tie (irrespective of gender)....
• brute force adj. Describes a primitive programming style
  one in which the programmer relies on the computer's processing power instead of using his or her own intelligence to simplify the problem, often ignoring problems of scale and applying naive methods suited to small problems directly to large ones....
• 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....
• moby /moh'bee/ [MIT: seems to have been in use among model railroad fans years ago.
  Derived from Melville's "Moby Dick" (some say from `Moby Pickle')....
• ill-behaved adj. 1. [numerical analysis] Said of an algorithm or computational method that tends to blow up because of accumulated roundoff error or poor convergence properties.
  2. Software that bypasses the defined OS interfaces to do things (like screen, keyboard, and disk I/O) itself, often in a way that depends on the hardware of the machine it is running on or which is nonportable or incompatible with other pieces of software....
• 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....