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.
No posts after this one, please.
Ok.
It is a miracle that curiosity survives formal education. - Einstein
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.
I agree with this method. If only to stave off the 1 minute edit-compile-edit approach a little longer.
The professor through Unix was the way it was because of punched cards?
Are you remembering that right?
Unix was an interactive system from the beginning.
Teletypes would explain the design of editor ed.
According to "The Development of The C Language" by Dennis Ritchie, Ken Thompson did some cross-development. Initially, he used a GE-635 machine, where he generated code for the PDP-7 that was put onto punched tape (not cards) and carried the PDP.
Business 101 teaches us that "cheap shit drives good shit out of the market"
That's down to the national culture.
Actually I have a theory it's related to the true rate of inflation (as opposed to the published level) within an economy.
Deleted
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.
"Second and subsequent assignments would use terminals"
...particularly the "unfortunately" part. It simply different products for different markets.
I would guess your dress shoes, for example, cost 10 bucks to make and involve lots of rubber, cardboard, glue and cheaply tanned low grade leather. My dress shoes probably cost $200 to make - and retail for $600. They are made in england by craftsman who use age old methods for tanning the select hide leather and sewn and glued to the oak bark soles and finished by hand.
Certainly the availability affordable goods has allowed for a higher standard of living as many "good enough" products are just that.
Terminals were plentiful around campus but CIS wouldn't let people use them.
Interesting. Sounds like the same mindset that wouldn't let students use pocket calculators.
The higher the technology, the sharper that two-edged sword.
The professor through Unix was the way it was because of punched cards? Are you remembering that right? Unix was an interactive system from the beginning.
The punch card influence manifested in the preference for keeping things brief, ideally within 80 columns. Some may focus on brevity due to "efficiency", 300 baud connections and such but 80 column terminal displays and 80 column printers also contributed to brevity.
Also while Unix was preferably used interactively there were environments where people were restricted to batch jobs. In another post I mentioned students taking cobol classes in the school of business being restricted to batch even though terminals were plentiful around campus.
I had a similar experience in the mid-70's, although the reason given was a bit different. The reason given was along the lines of we should learn how to structure and write our code carefully because programming in a batch environment with cards made fixing bugs so painful.
Of course, this mentality went back to the thinking that cards, card readers, and 132 column line printer output was something that was done through surly RJE operators. In that environment you pushed your deck through the service window, being very careful to be friendly to the operator if they were at the window (that tended to get your deck done first or, if you later had a "rush job", they would actually get off their butts and submit your job like NOW even though policy didn't require it), and then came back four to 24 hours later to get your listing and experience that sinking feeling when you saw that the output listing was way too thin and must just be compiler error output.
What the school missed was that they had decided not to bother with RJE operators - instead they had rooms with key punches, a high speed (relatively) card reader to submit jobs, and a printer right next to it. Oh, and the output usually was available in a minute or two (the printer was the bottleneck). So, the whole experience wasn't quite what the school intended. Fortunately, they only did this in one of the early courses -- other than that they were quite advanced for the day.
Unfortunately I got a summer job (and subsequent part time job during the school year) a couple years later at a major aerospace firm working for a guy who still believed in cards and maintaining and enhancing a program he kept on cards. Yech, that's when I learned about being friendly to surly operators (it worked - a smile, "Nice weather isn't it?", "Hope your hemorrhoids are better", and the like really did get jobs run more quickly!). Fortunately, after a few weeks, a coworker took pity on me and showed me how to get the program card deck online, edit it via TSO, and just punch a whole new box of cards with the current program on it whenever my boss became uncomfortable because he didn't have "his program" "safely" on his bookshelf in a box of cards. A lot of trees died unnecessarily that year and I have no idea, to this day, how the RJE operator's hemorrhoids did after that.
I had a similar experience in the mid-70's, although the reason given was a bit different. The reason given was along the lines of we should learn how to structure and write our code carefully because programming in a batch environment with cards made fixing bugs so painful.
So did you write out your programs by hand on Fortran coding forms, a specialized pad of paper with 80 columns and color coding to indicate label, comment, code, continuation and sequence number fields?
:-)
We were told that in the really bad old days programmers filled out these forms by hand and gave them to data entry people who punched your cards for you. Some old timers had two bottlenecks to kiss up to.
Read the literature when they were being widely used.
It is NOT 'PUNCH' card, nor are the things that are punched out 'CHAD'
They are 'CHIPS', and accumulate into a 'CHIP BUCKET'.
I see that exactly ONE person has used 'PUNCHED' correctly in the replies.
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!
Is there a device that can be connected to a PC that will read punch cards? Does the iPhone have an app yet? I have simh! http://simh.trailing-edge.com/ I need to feel the smell expensive cardboard and heard grinding noises (make sure that app does sound effects!)
I started on the C-64. My only nostalgia is for the sound of a non-audio processing tape drive!
I'd go on a Vegan diet but the delivery time from Vega is too long. --brownkitty
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.
I'll take the bait.
Actually, advances in programming languages and user interfaces on computerized machine tools went along with the re-skilling of factory workers. See, when there was no effective UI, it was a selling point that the Managers would have to program the machines or hire consultants to do it.
Admittedly, a number of factors went into reversing this situation. Perhaps most importantly, the products of the preprogrammed machines were mostly junk, and the market didn't want them. Cause and effect is hard or impossible to pin down. However, yeah, when the workers regained control of their machines, there was an improved UI.
Keeping things hard always doesn't benefit the practitioner; making things easier doesn't always deskill them. We just need to keep trying to find the natural correspondence, and this is a slow and inefficient process exactly because we're human.
"They were pure niggers." – Noam Chomsky
I'm reminded of a blog post I read wherein a guy defended his gas-guzzling muscle car (which he liked anyway) by saying it held together much longer than a regular vehicle would, the higher gasoline usage being offset by the lower use of manufacturing resources.
I listen to both RIAA and non-RIAA stuff if I like the music, tangential business/politics nonwithstanding.
I *am* a business major, and one of the most consistent themes from my professors is that responsible behavior is supposedly financially better in the long run anyways, in addition to whatever ethical/moral claims involved.
I listen to both RIAA and non-RIAA stuff if I like the music, tangential business/politics nonwithstanding.
Interesting article, wonder what will become of the machine and its last operator?
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.
Okay. I'll buy that.
The higher the technology, the sharper that two-edged sword.
I used Fortran for some run of the mill, ordinary, regular business LOB apps consulting work a few years ago. A scientist had a simulation that he originally wrote in Fortran, and had been ported poorly to VB6 a while back. He needed some changes, so I referred to the original fortran code to understand his intent. No biggie.
Scientific programming is a blast.
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
This reminds me, back in the forties or fifties my grandad obtained an ugly dresser and it came with a punch card taped to the back. The dresser was a real piece of crap but that punch card made it worthwhile. How many people can say they own an honest to god real punch card. Sadly the punch card disappeared and with out it, the ugly dresser had no business being owned by me and so I sold it. Hopefully this lace business sticks around, those old time machines are a real treat to watch as they work.
My Web Site
yep I used to enter FORTRAN programs that the research engineers wrote by hand on forms at my first Job.
This isn't so much about "programming" as it is about a nearly dead industry.
Who would want to work as "skilled labour" in the last plant of an entire industry in the country, especially when they expect to pay "starter" wages for 5-7 years? As a techie it would be fun to work at a company like that and learn everything about the machines, even invent better ones. The problem is that this company really doesn't have a budget to teach anybody, they don't have a budget to invent machines... they just want folks to work at a literally dean-end job.
We need a version of the SCA for 1850's to 1970's! we can all dress up like shop workers and build machines... like steampunk, only more boring.
That doesn't surprise me in the least. At school we only rote learned our times tables up to 12, and even then 11 and 12 were introduced later so aren't as ingrained in my brain. So for 9 x 13, I'd have to think about it long enough that a calculator would probably be faster if it was close at hand.
9 x 13 = 10 x 13 - 13, so you really don't need the calculator.
I spent some quality years programming basic and - later on - machine code (there weren't too many assemblers lying around I, as a kid, I didn't know about them). Then I got to high school and thought that blind, 10 finger typing would be useful. For this I had to stay at school for 2 hours without lessons (I didn't do any homework at high school, so this was a bore). Imagine my surprise when I found out that typing was done using actual *typewriters*, placed next to the computer class. Dropped it after 5 minutes, got some typing tutorials for my computer and I'm probably the fastest writer of documentation at my software engineering job.
Then again, the IDIOTS at the "Vrije Universiteit" still required me to learn emacs and VI to do compiler construction and operating systems. That didn't end well - and I still absolutely abhor text editors like those.
This really doesn't obviate the point. Of course you don't need a calculator for 9x13. I rarely used a calculator in college, and I can approximate logarithms in my head well enough to pass a chemistry quiz. This said, when I HAVE a calculator at hand, I'm likely to use it for 9x13, it will be faster. (I can do Start -> Calculator and punch it in in about the same time, and then I have calculator open for the next problem.)
I'm the only gay eskimo in my tribe
Funnyhacks - Wierd, unusual, and fun hacks
Of course I don't need the calculator, but I was pointing out that there is a cost/benefit analysis for this type of thing - if the calculator is already there ready to accept input, then the cost of using the calculator for such a seemingly simple problem is very low. If I have to reach into my bag, or go down to the Start Menu, or into the menus on my phone, then the cost becomes higher and I am more likely to work it out in my head.
It may be true that it was useful, but I wish they hadn't made so many buisness majors do punch-card programming. I can't tell you how fucking sick I am of hearing some 40-something break into how they took programming in college, so they "know a little about it". This has been from entry level workers to CEO's. None of them had, or have a clue.
No comprende? Let me type that a little slower for you...
I did not drop the class; I learned JCL, too; learned how to duplicate decks, sort them with a big sorting machine, "interpret" them (don't ask); even program the keypunch terminals themselves (with a punch card -- what a shock); and so on.
One day a couple years later a 3330 pack at my summer-job company (a research organization) crapped, wiping out a whole project related to the Space Shuttle. My boss had made sure our little sub-organization was completely backed up on cards, and so we smiled right through the incident. The rest of the folks, not so much.
There's nothing like the confidence that comes from a box of cards. It's not going anywhere; it won't drop any bits over time; it won't decay like a DVD or CD. I loved cards in a way, even though I hated using them and dealing with them. And that 3270 terminal was SLOW and EXPENSIVE compared to cards. We could copy a file with a skinny little IEBGENER deck for pennies, while logging into TSO to accomplish the same thing could be $10 or more, and cost you many minutes of waiting for the (overloaded) system to respond. Yes, that's right, we paid for every machine cycle with real money.
It may be true that it was useful, but I wish they hadn't made so many buisness majors do punch-card programming. I can't tell you how fucking sick I am of hearing some 40-something break into how they took programming in college, so they "know a little about it". This has been from entry level workers to CEO's. None of them had, or have a clue.
We computer science majors are guilty of such things too. For example we take an electrical engineering class or two and think we know how to design hardware. My first job out of college was doing a kernel for a custom motherboard. The hardware guys were a little distant until they got to know me and saw that while I could often follow/participate in conversations I had no delusion about being proficient in electrical engineering, but more importantly I did not cry wolf and blame the hardware when I didn't understand why the software was crashing.
There's nothing like the confidence that comes from a box of cards.
Basically you're saying there's nothing like a relatively stable medium made from wood. Just like books, and I agree with you. My problem was less that I would have to use punch cards, but that I would have to spend time on a mainframe. I had little interest in mainframe programming at that point: I had already decided that microprocessors were were I wanted to be.
The higher the technology, the sharper that two-edged sword.
I did at first (this was university, late 1960's). Even after I'd located most of the public-access keypunch machines, I still made a point of sending in a few forms a week to keypunch central, it made a good excuse to chat up the chicks there. If I could get past the head dragoness who guarded them!
I never had to do that for a job, but I did in school. My high school had a programming class that let us run programs on the administration's computer, a Honeywell 200 if I recall correctly. We wrote our programs on those coding forms (COBOL and FORTRAN, maybe some sort of assembler also), and they were sent by campus mail to the central office, punched by data entry clerks, run by the operators, and we got the cards and printout back in the next day's campus mail. 23 hour turnaround, best case. If they were busy, maybe an extra day. And we never had any contact at all with the operator, so there was no chance to kiss up to them.
We also had access to a HP 2000 system via teletype, which did BASIC only. We used paper tape with that one.
This was in the mid-1970s.
I hope fortran rest in peace now.