See also {attoparsec}, {calculator}, {chemist},
{console jockey}, {fish}, {go-faster stripes},
{grunge}, {hakspek}, {heavy metal}, {leaky heap},
{lord high fixer}, {loose bytes}, {muddie}, {nadger},
{noddy}, {psychedelicware}, {plingnet}, {raster
blaster}, {RTBM}, {seggie}, {spod}, {sun lounge},
{terminal junkie}, {tick-list features}, {weeble},
{weasel}, {YABA}, and notes or definitions under {Bad
Thing}, {barf}, {bogus}, {bum}, {chase pointers},
{cosmic rays}, {crippleware}, {crunch}, {dodgy},
{gonk}, {hamster}, {hardwarily}, {mess-dos},
{nybble}, {proglet}, {root}, {SEX}, {tweak}, and
{xyzzy}.

:compact: /adj./ Of a design, describes the valuable property
that it can all be apprehended at once in one's head. This
generally means the thing created from the design can be used with
greater facility and fewer errors than an equivalent tool that is
not compact. Compactness does not imply triviality or lack of
power; for example, C is compact and FORTRAN is not, but C is more
powerful than FORTRAN. Designs become non-compact through
accreting {feature}s and {cruft} that don't merge cleanly
into the overall design scheme (thus, some fans of {Classic C}
maintain that ANSI C is no longer compact).

:compiler jock: /n./ See {jock} (sense 2).

:compress: [Unix] /vt./ When used without a qualifier,
generally refers to {crunch}ing of a file using a particular C