The Jargon File, Version 4.0.0, 24 Jul 1996 by Various
page 83 of 773 (10%)
page 83 of 773 (10%)
![]() | ![]() |
|
someone is going to let a new party maintain a piece of code.
Conceptually analogous to an operating system {core dump} in that it saves a lot of useful {state} before an exit. "You'll have to give me a brain dump on FOOBAR before you start your new job at HackerCorp." See {core dump} (sense 4). At Sun, this is also known as `TOI' (transfer of information). :brain fart: /n./ The actual result of a {braino}, as opposed to the mental glitch that is the braino itself. E.g., typing `dir' on a Unix box after a session with DOS. :brain-damaged: /adj./ 1. [generalization of `Honeywell Brain Damage' (HBD), a theoretical disease invented to explain certain utter cretinisms in Honeywell {{Multics}}] /adj./ Obviously wrong; {cretinous}; {demented}. There is an implication that the person responsible must have suffered brain damage, because he should have known better. Calling something brain-damaged is really bad; it also implies it is unusable, and that its failure to work is due to poor design rather than some accident. "Only six monocase characters per file name? Now *that's* brain-damaged!" 2. [esp. in the Mac world] May refer to free demonstration software that has been deliberately crippled in some way so as not to compete with the commercial product it is intended to sell. Syn. {crippleware}. :brain-dead: /adj./ Brain-damaged in the extreme. It tends to imply terminal design failure rather than malfunction or simple stupidity. "This comm program doesn't know how to send a break -- how brain-dead!" |
|