Not quite the true experience. It should first start with writing the program on a standard coding form (https://commons.wikimedia.org/wiki/File:FortranCodingFo

Not quite the true experience. It should first start with writing the program on a standard coding form (https://commons.wikimedia.org/wiki/File:FortranCodingForm.png https://commons.wikimedia.org/wiki/File:FortranCodingForm.pn...), after which it is sent to the keypunch department. When the deck and card listing come back the next day, the programmer would proofread the listing and use a Type 029 to replace misspunched cards and insert/delete to correct bugs found in re-reading. This was somewhat laborious, since most programmers did not type well, and unlike the simulation, the 029 did not have a backspace key. JCL or other control language cards as needed by the operating system would have to be punched to define memory needed, tape drives, disk drives, department chargeback accounts, etc. And the output would come back after a few hours on 132 column greenbar fanfold.