Related:

• bottom-up implementation: n. Hackish opposite of the techspeak term `top-down design'.
  It is now received wisdom in most programming cultures that it is best to design from higher levels of abstraction down to lower, specifying sequences of action in increasing detail until you get to actual code....
• 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....
• Internet n. The mother of all networks. First incarnated beginning in 1969 as the ARPANET, a U.
  S. Department of Defense research testbed. Though it has been widely believed that the goal was to develop a network architecture for military command-and-control that could survive disruptions up to and including nuclear war, this is a myth...
• 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....
• middle-out implementation See bottom-up implementation.
• bare metal n. 1. [common] New computer hardware, unadorned with such snares and delusions as an operating system, an bit bashing needed to create these basic tools for a new machine.
  Real bare-metal programming involves things like building boot proms and BIOS chips, implementing basic monitors used to test device drivers, and writing the assemblers that will be used to write the compiler back ends that will give the new machine a real development environment....
• Wrong Thing: n. A design, action, or decision that is clearly incorrect or inappropriate.
  Often capitalized; always emphasized in speech as if capitalized....
• 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....
• heavyweight adj. [common] High-overhead; baroque
  code-intensive; featureful, but costly. Esp. used of communication protocols, language designs, and any sort of implementation in which maximum generality and/or ease of implementation has been pushed at the expense of mundane considerations such as speed, memory utilization, and startup time....