Related:

• brain dump n. [common] The act of telling someone everything one knows about a particular topic or project.
  Typically used when someone is going to let a new party maintain a piece of code....
• core dump: n. [common {Iron Age} jargon, preserved by UNIX] 1.
  [techspeak] A copy of the contents of {core}, produced when a process is aborted by certain kinds of internal error....
• core dump n. [common Iron Age jargon, preserved by Unix] 1.
  [techspeak] A copy of the contents of core, produced when a process is aborted by certain kinds of internal error....
• dump: n. 1. An undigested and voluminous mass of information about a problem or the state of a system
  especially one routed to the slowest available output device (compare {core dump}), and most especially one consisting of hex or octal {runes} describing the byte-by-byte state of memory, mass storage, or some file....
• chase pointers: 1. vi. To go through multiple levels of indirection, as in traversing a linked list or graph structure.
  Used esp. by programmers in C, where explicit pointers are a very common data type....
• bits: n.pl. 1. Information. Examples: "I need some bits about file formats.
  ("I need to know about file formats.") Compare {core dump}, sense 4....
• uke: /n[y]ook/ vt. 1. To intentionally delete the entire contents of a given directory or storage volume.
  On UNIX, `rm -r /usr' will nuke everything in the usr filesystem....
• dump n. 1. An undigested and voluminous mass of information about a problem or the state of a system
  especially one routed to the slowest available output device (compare core dump), and most especially one consisting of hex or octal runes describing the byte-by-byte state of memory, mass storage, or some file....
• core: n. Main storage or RAM. Dates from the days of ferrite-core memory
  ow archaic as techspeak most places outside IBM, but also still used in the UNIX community and by old-time hackers or those who would sound like them....