Cruel! The usual solution was to take a marker and swipe the deck along the top side, in a diagonal, so they are much easier to sort. You might recall that Fo

Cruel! The usual solution was to take a marker and swipe the deck along the top side, in a diagonal, so they are much easier to sort. You might recall that Fortran ignored everything beyond column 72. This was where you put the 'sequence number', aka line number, so when you drop the deck you stick the cards the sorting machine and voila, it's ordered again. Ahh, I see Wikipedia covers this bit of arcana, at https://en.wikipedia.org/wiki/Computer_programming_in_the_punched_card_era#Columns_73-80 https://en.wikipedia.org/wiki/Computer_programming_in_the_pu... . But there are many stories of the heartbreak of those who didn't take one of these precautions. Ha! In looking for one I came across http://www.columbia.edu/cu/computinghistory/sorter.html http://www.columbia.edu/cu/computinghistory/sorter.html : > You may have heard the story of the operator who dropped a whole box of cards. Wanting to put things right as quickly as possible, he sorted the cards, without consulting the user. As it turned out, that was the worst possible response. Up until that point, the box had contained a sample of random numbers. –Ted Powell, Dec 2006