My first coding experience was as a kid on punch cards (and I’m not even 60 yet). This was in the late 70s and I had an older neighbor friend who was in high school but taking some classes at the local university. The intro programming class that he took still used punch cards on mainframes (though this was being phased out even then) and my friend sort of Tom-Sawyered me into helping him with his homework. It was actually kind of fun to sit there punching the holes in the cards, and then we’d take the stack of cards over to the CS building and leave it in his mail slot, and then a few days later you’d get a giant stack of that old green- and white-striped computer printout paper deposited there with the program’s results.
It’s interesting, it really taught me to check and recheck my own code extremely thoroughly and carefully before “running” it, rather than pumping out some slop quickly and relying on the compiler and/or the output to identify any problems. Because with multiple days between submitting the code and seeing the results, you really had to make sure stuff was working from the get-go. In my career as a programmer, I subsequently ran into many similar situations that required basically just your own eyeballs to make sure the code was right. When I was writing Blackberry applications circa 2010 (!) for example, RIM’s utterly fucked-up developer environment meant that the delay between starting to compile an application and having it running on a test device could be 30-45 minutes or more (if it finished compiling at all) even if I’d only made a single one-line code change. So I had to get back in the habit of very carefully writing a lot of code before attempting to compile, and making sure it was going to work correctly just by inspection.
My first coding experience was as a kid on punch cards (and I’m not even 60 yet). This was in the late 70s and I had an older neighbor friend who was in high school but taking some classes at the local university. The intro programming class that he took still used punch cards on mainframes (though this was being phased out even then) and my friend sort of Tom-Sawyered me into helping him with his homework. It was actually kind of fun to sit there punching the holes in the cards, and then we’d take the stack of cards over to the CS building and leave it in his mail slot, and then a few days later you’d get a giant stack of that old green- and white-striped computer printout paper deposited there with the program’s results.
It’s interesting, it really taught me to check and recheck my own code extremely thoroughly and carefully before “running” it, rather than pumping out some slop quickly and relying on the compiler and/or the output to identify any problems. Because with multiple days between submitting the code and seeing the results, you really had to make sure stuff was working from the get-go. In my career as a programmer, I subsequently ran into many similar situations that required basically just your own eyeballs to make sure the code was right. When I was writing Blackberry applications circa 2010 (!) for example, RIM’s utterly fucked-up developer environment meant that the delay between starting to compile an application and having it running on a test device could be 30-45 minutes or more (if it finished compiling at all) even if I’d only made a single one-line code change. So I had to get back in the habit of very carefully writing a lot of code before attempting to compile, and making sure it was going to work correctly just by inspection.