Abhishek S.
Shipping in public. Listening in private.

Abhishek

I lead women’s Indo-Western & Premium at Max Fashion. I also wrote the AI that runs the buying floor.

Rare profile. Category operator who ships production code.

Senior Buying Leader · Max Fashion Women’s Indo-Western & Premium · 530+ India stores NIFT ’12 · Twelve years on the floor

abhishek@bengaluru ~ %
>role: senior buying lead
>dept: women’s indo-western + premium
>floor: 530+ stores india

The Jacquard Loom

A silk portrait of Joseph-Marie Jacquard once required about 24,000 punched cards to weave a single image. That is the reason the Jacquard loom belongs in computing history: not because it calculated, but because it made a machine obey stored instructions. Patented in 1804 in Lyon, the loom turned textile patterning into a chain of reusable, copyable commands.

At a glance

The first programmable machine was a textile loom. Computing inherited its memory format for 170 years.

How it worked

The Jacquard attachment sat on top of a loom and controlled which warp threads rose for each pass of the weft. Each card represented one row of the pattern. A hole let a pin pass through; no hole blocked the pin. That yes-or-no decision lifted or did not lift a thread.

The machine did not invent weaving patterns. Basile Bouchon used perforated paper in 1725, Jean-Baptiste Falcon used linked cards in 1728, and Jacques Vaucanson built an automated loom mechanism in the 1740s. Jacquard’s achievement was combining these ideas into a practical attachment that could be fitted to looms and operated at scale.

The key move was separation: the loom was generic, the pattern lived outside it. Change the card chain and the same machine could weave flowers, brocade, a portrait, or a repeating border. Early setups used hundreds of hooks; later versions could control more than 1,000 warp ends.

Why computing people care

Charles Babbage saw the Jacquard loom as proof that physical cards could control a sequence of machine actions. His Analytical Engine, designed in the 1830s and never completed in his lifetime, used punched cards for operations and variables. Ada Lovelace made the famous comparison in 1843: the Analytical Engine “weaves algebraical patterns just as the Jacquard-loom weaves flowers and leaves.”

Herman Hollerith later used punched cards to tabulate the 1890 U.S. Census. His cards were read electrically, not mechanically, but the control idea stayed recognizable: a hole is a decision. Hollerith’s company became part of CTR in 1911; CTR became IBM in 1924. IBM’s 80-column card, standardized in 1928, stayed in heavy use into the 1970s.

The sharp line is this: Jacquard did not make a computer, but he helped make instructions into an object.

The artifact that makes the point

The woven portrait of Jacquard is the sticky object here. It was not painted on silk. It was encoded into cards, read row by row, and regenerated by a loom. Babbage owned a copy; one survives in the Science Museum in London, and another is associated with the Computer History Museum’s computing-history narrative.

A portrait made of instructions is closer to a program than to a picture. The image was not just stored. It was executable by a machine.

What's contested

The ancestry claim gets overstated. A Jacquard loom is not a general-purpose computer, and punched media also appear in player pianos, automated organs, and industrial control. The causal chain from Jacquard to Babbage is well documented; the claim that textiles “invented computing” is too neat.

The deeper dispute is whether the loom matters as engineering or as metaphor. Babbage borrowed the card idea, but the Analytical Engine’s arithmetic, memory, and control flow came from mathematics and mechanical calculation. The loom supplied a way to externalize command, not the whole architecture of computing.

Why this has to do with other realms

The Jacquard loom makes concept fabric as data literal: cloth becomes a grid of decisions, and design becomes information before it becomes matter. That bridge runs the other way too. Modern software looks immaterial until it meets a factory, a screen, a robot arm, or a genome sequencer.

There is also a philosophy thread. person ada lovelace saw that a machine following symbolic rules might manipulate music, language, or images, not just numbers. The loom made that leap easier to see because it turned symbols into flowers before computers turned symbols into everything else.

Key Sources

Further Reading

Abhishek's take

The part I watch recur is simpler than the history: pattern lives outside the machine. On a buying floor, when the design file, the trim card, and the weave specification all travel separately from the loom or factory, you can swap one without touching the others. I have seen seasons where we changed a yarn count or a weave repeat four weeks before bulk and the factory treated it as a near-impossible ask because they had baked the pattern into their setup rather than reading it fresh each time. Jacquard solved that in 1805. The instruction should be copyable and separable from the mechanism that executes it. Every tool I have written for the floor is built on that same separation: the range logic does not live inside the spreadsheet; the spreadsheet just reads it.

See Also

Open question

If the first programmable machines grew out of looms, music boxes, and census offices, what other “non-computing” machines are quietly teaching the next century how to think?