/dek'l/
noun — “two nickels pretending to be a word size.”
[from dec- and nickle]
Deckle is hacker jargon for a quantity of 10 bits, formed by combining two nickles (where a nickle represents 5 bits). Like its smaller relative, the term emerged not from formal standards but from developers trying to describe unusual hardware layouts that did not fit neatly into the byte-oriented vocabulary that later became dominant.
The name itself is intentionally playful: dec- for ten, fused with nickle to preserve the family resemblance. Rather than repeatedly saying “ten-bit quantity” or “ten-bit word,” developers coined a term that was shorter, easier to say, and mildly entertaining—which is surprisingly common in computing culture.
The term has been reported among developers working with the Mattel GI 1600, the processor used in the Intellivision game console. That architecture contained an unusual split: 16-bit-wide RAM paired with 10-bit-wide ROM. Once systems begin storing and processing values in widths that do not align with standard Byte boundaries, ordinary terminology becomes awkward and jargon begins filling the gaps.
In that context, a deckle became a convenient way to think about a full ROM-width value:
// one deckle (10 bits)
1010101110
// viewed as two nickles
10101 01110
// 5 bits + 5 bits = 10 bitsUnlike modern architectures, which generally standardize around bytes and powers of two, earlier hardware sometimes experimented freely with storage widths, instruction lengths, and memory organization. A ten-bit ROM no longer seems especially strange once enough engineers start building around it—but language still has to catch up.
Numerically, a single deckle can represent values in this range:
// 10-bit range
0000000000 = 0
1111111111 = 1023
// total possible values:
// 1024Terms like deckle illustrate an overlooked side of computing history: units are not always universal. Today, developers casually assume that information naturally arrives in bytes, kilobytes, and megabytes, but that neat hierarchy emerged through standardization. Earlier machines occasionally wandered into stranger territories where ten bits was perfectly ordinary and somebody eventually decided it deserved a name.
Conceptually, a deckle is less important as a unit than as evidence of how programmers think. When existing vocabulary becomes inconvenient, engineers tend to invent new language rather than repeatedly explain old constraints. Computing history is full of these tiny linguistic hacks.