The Last of the Punch Card Programmers
Peter Cus writes "Cluny Lace, an English lacemaking manufacturer, has reverted to 19th-Century Leavers machines in order to stay competitive. These 19th-Century machines use Jacquard punch cards. Ian Elm, thought to be the last of the card punchers, says young people don't want factory work: 'Younger people coming into a trade want a guarantee of a career out of it, and this is so uncertain.'"
There's something more that the article did not mention. It's not as if 19th century technology has been forgotten already.
If there is a market for it, you can be sure someone will build a modern machine to do it better, faster, and cheaper than those old machines do.
What we really need is for people to RTFA before they comment.
Given how long I've been out of work, I'd take any offer of employment at this point. Punch cards would be swell.
CS Bachelor's degree and 20 years experience mean jack shit in this economy.
They hand plant each blade of grass for that high quality finish!
My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine
Is it programming if the output is basically a copy of the program?
Or is it data entry?
To BBC's credit, nowhere does "program" appear in the original article.
Punch cards can be a pretty useful educational tool. In the 1980s I had an intro to computer science class where we had to write our first programming assignment in fortran(*) using punch cards. Second and subsequent assignments would use terminals. The professor explained that doing so was terribly obsolete but that this experience would help us understand why some computer languages (fortran in particular) and some operating systems (including unix) are the way they are. He added that the deck of blank punch cards we would have to buy would also provide us with plenty of book marks for the rest of our years in college.
(*) Fortran was only used in this intro computer science class. This class was required for many engineering and science majors who were more likely to use fortran than computer science majors. Unexpectedly in the mid 1990s I actually used fortran as my company was contracted to move some chemistry software from mainframes to personal computers.
The evidence is generally for faster/cheaper.
Indeed. Business 101 teaches us that "cheap shit drives good shit out of the market" in a race to the bottom. Business 201 modifies this slightly by noting that statutory regulations and standards usually place a lower bound on how shitty stuff can get. MBA courses subsequently add an "unfortunately" to the latter observation.
Those who can make you believe absurdities can make you commit atrocities. - Voltaire
In the 1980s I had an intro to computer science class where we had to write our first programming assignment in fortran(*) using punch cards.
Back in the 1970's when I was in college, the first day of my first computer class the professor told us that "the keypunch machines are down the hall." I asked him, "uh, as in punch cards?" At that point I'd been hacking assembler code on microcomputers for a few years and doing real-world interfacing, and really wasn't interested in punch cards. Sure, had it been a one-time experience like you had, that would have been interesting. But an entire school year spent in front of a keypunch machine, submitting jobs to an IBM 370, when there were rooms full of 3270 terminals all over the place? No thanks. I dropped that class that afternoon.
The higher the technology, the sharper that two-edged sword.
At my university in the 1980s there were two "programming" degrees. The school of science offered Computer Science (CS) and the school of business offered Computer Information Systems (CIS). This is not standard nomenclature, at other universities CIS is from the school of mathematics or science. The CIS folks were still using punch cards for their COBOL programming. I knew a few folks who transferred to CS because of the requirement to use punch cards. Terminals were plentiful around campus but CIS wouldn't let people use them.
Figures it would be a guy that loves lace.
+0 Meh
I well remember punching decks of cards for my Computer Science classes, then "submitting" them to the guy behind the bank-teller window in the Mainframe Suite and waiting for my job to finish so another guy could hand me a thick stack of folded paper from the LinePrinter so I could see if my program had worked. I always got a laugh out of waiting an hour or more for my printout, which proclaimed on the second page that I had consumed .00058 seconds of CPU time -- talk about a responsive user interface!
John Leavers invented those machines in 1812 and they're still in use. If two hundred years isn't job security, I don't know what is!
In those days, UNIX ran on machines that we would consider tiny today, and so it had small input buffers, which you might say it was influenced by the 80-column punched card, or perhaps just by the 32k bytes (or 64k or 128k, if you were rich) PDP-11 system memory size. These buffer size limits were in the kernel, but easier to see in the /bin utilities.
The level of calculator use depends on the level of the student - the number of times I've seen my students reach for a calculator for simple arithmetic (9 x 13) or similar worries me that they don't truly understand what they are doing. Much of the basic arithmetic helps inform the algebra usage in later classes, which is why things like long division are still relevant. I relented and allow non-symbolic manipulation calculators for my calc classes these days after a student pointed out that their cell phones meant they have a calculator permanently available. I also make a point of assigning a problem or two that the TI-89's choke on to explain why learning the techniques directly is important.
But an entire school year spent in front of a keypunch machine, submitting jobs to an IBM 370, when there were rooms full of 3270 terminals all over the place? No thanks. I dropped that class that afternoon.
I'd been programming on terminals for several years before college, and one of my first college classes required us to punch cards as well. I'll say it's worth the experience, once, but you did the right thing in avoiding a whole year of it.
In some respects, punch cards are to teaching programming as film is to teaching photography. The problem is that the cost of any operation is high (you had to wait hours for your results in the case of punch cards, just as film was very expensive) so you did things differently. You'd waste hours of time scouring your deck for syntax errors. Or you'd take only one photo of an interesting scene, saving those other 35 exposures for other interesting scenes.
With digital photography, you can take a dozen shots with different settings in hopes that one will turn out spectacular. With compilers being virtually instant, practices like test driven development are possible, where you write a test, bang out some code to pass it, then move on.
I always think it's good to know about the past, but that doesn't mean we should remain stuck living in it.
John