The punch card began as a way to count a nation. Herman Hollerith punched the 1890 United States census onto cards, feeding a population through a machine that could read holes far faster than any clerk could read handwriting. The idea worked so well that it outgrew the census entirely, and in 1928 IBM standardised the eighty-column card, fixing a width that would govern computing for the next half century.

On that card, one card meant one line. A program was a physical stack, a deck you could hold and drop and reorder, each card carrying a single instruction. When terminals arrived, they inherited the same measurement, because a screen row was built to hold exactly what a card held: eighty columns, no more. That inheritance never quite went away. It is why eighty columns still polices code style today, why style guides and editors draw their margins at that number, long after the last card was punched. A convention set by cardboard now lives in software written by people who have never seen one.

The cards also taught a lesson in caution that the exhibit is fond of. Careful programmers reserved the final columns of each card for sequence numbers, small identifiers that meant nothing to the program but everything to its keeper. If a deck slipped from your hands and scattered across the floor, those numbers let a machine sort the shuffled cards back into order, reassembling the program from chaos. The precaution reveals how fragile the whole arrangement was: your work existed as a physical sequence that gravity could undo in an instant. Visitors can still feel that fragility by punching their own card at the exhibit's workshop, where the holes are made one at a time and the width is, of course, eighty columns. It is a small way of touching a standard that shaped an industry and then quietly refused to leave it.