Craig R. McClanahan wrote: >On Fri, 9 Aug 2002, Martin Cooper wrote: > >>Whoa, this thread is making me feel sooo old! >> >>In my first job, I had to write the code on coding sheets, which were then >>given to a pool of drones who turned the code into punched cards. The boxes >>of cards would then go to the sysops, who would eventually find time to feed >>them into an ICL mainframe. Then I got back a code listing with all my >>compilation errors. Once I'd finally got the code to run, the usual early >>results were a two inch thick core dump. Talk about a long edit-compile-run >>cycle! >> >I had that experience in college as well. It was particularly frustrating >when taking my Comp Sci classes to have only twice-a-day turnaround on >simple typos that led to compile errors -- so I got myself hired as the >computer operator who ran the student jobs (and I could run *mine* as >often as I wanted to :-). > ... and got paid to do it - you gotta love that ;-)
>Slightly later, and much to my chagrin, my wife (a computer literate end >user, but by no means a geek) figured out that punched cards gave her a >lot of power over me. It seems that we were at the computer center pretty >late one night, waiting for "just one more run" ... we all know how that >goes, right? So she picked up the source code cards for the program I was >working on (with no sequence numbers, of course) and said, "if you don't >feed me NOW, I'm going to DROP these ...". > LOL!!! That is SO something my wife would wind up doing if we used punch cards today! -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
