Related:

• manularity: /man`yoo-la'ri-tee/ [prob. fr. techspeak `manual' + `granularity'] n.
  A notional measure of the manual labor required for some task, particularly one of the sort that automation is supposed to eliminate....
• menuitis: /men`yoo-i:'tis/ n. Notional disease suffered by software with an obsessively simple-minded menu interface and no escape.
  Hackers find this intensely irritating and much prefer the flexibility of command-line or language-style interfaces, especially those customizable via macros or a special-purpose language in which one can encode useful hacks....
• app: /ap/ n. Short for `application program', as opposed to a systems program.
  Apps are what systems vendors are forever chasing developers to create for their environments so they can sell more boxes....
• T: /T/ 1. [from LISP terminology for `true'] Yes. Used in reply to a question (particularly one asked using {The `-P' convention}).
  In LISP, the constant T means `true', among other things....
• oolsmith: n. The software equivalent of a tool-and-die speciali
  one who specializes in making the {tool}s with which other programmers create applications....
• ext: n. 1. [techspeak] Executable code, esp. a `pure code' portion shared between multiple instances of a program running in a multitasking OS.
  Compare {English}. 2. Textual material in the mainstream sense...
• app /ap/ n. Short for `application program', as opposed to a systems program.
  Apps are what systems vendors are forever chasing developers to create for their environments so they can sell more boxes....
• heavyweight: adj. 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....
• 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....