3 ms·
Jacquard was the first to build a stored program machine. It didn't compute, but it did produce valuable programmed output. Thus the people who punched the card
by mikewarot 5y ago
Jacquard was the first to build a stored program machine. It didn't compute, but it did produce valuable programmed output. Thus the people who punched the cards for looms were programmers.
When Henry Maudslay designed, built and set up his 16 machines to make pulleys for the Royal Navy, he was also doing programming.
I think the main point of the article is that we need to greatly broaden the idea of what programming means. It doesn't have to involve a program counter iterating through a list of instructions.
Spreadsheets don't have a program counter (though of course, we use them in the process of making them work). Field Programmable Gate Arrays also don't have a program counter, and they do everything in parallel, yet they are programmed.
Programming is the process of breaking a problem down to a series of steps that are then mechanized.
- FearNotDaniel 5y agoI also thought of Jacquard as I was reading this. But that's not the point of the article at all. I'm with you 100%, it is useful and constructive to consider other programming-like disciplines and potentially consider retroactively naming them 'programs' (e.g. as a child first learning to code I was fascinated by my grandmother's knitting patterns, they seemed very similar to the programs I was learning to write). But that's not what is under discussion here: this is about actual uses of the word 'program(me)' in computing contexts and their precursors, and specifically whether credit for invention of that term belongs to the theoreticians or the engineers, which has broader implications in how we approach the field of computing today.