For anyone who wants to experience the first part of this process, here is a FORTRAN Coding Form (in caps because that's how it was spelled back then): https:/

For anyone who wants to experience the first part of this process, here is a FORTRAN Coding Form (in caps because that's how it was spelled back then): https://upload.wikimedia.org/wikipedia/commons/1/18/FortranCodingForm.png https://upload.wikimedia.org/wikipedia/commons/1/18/FortranC... Print that in color on 8½x14" (legal size) paper and get to work! Of course there were a few other steps in the programming process back then. 1. A Systems Analyst took business requirements and turned them into an overview diagram of the system structure. 2. A Programmer took those diagrams and drew detailed flowcharts. These included every "if" statement, every loop, every detail. They were in effect code, but in a diagram form. Don't forget your IBM Flowcharting Template! https://ids.si.edu/ids/deliveryService?id=NMAH-AHB2012q05389 https://ids.si.edu/ids/deliveryService?id=NMAH-AHB2012q05389 3. A Coder read the programmer's flowcharts and wrote out the equivalent FORTRAN code on multiple pages of Coding Forms. 4. A Keypunch Operator read the Coder's forms and punched them onto cards, one card for each line of a Coding Form. 5. Finally we get to the High Priest of this operation. A Computer Operator - the only person allowed to touch the Computer! - ran your deck of cards through the machine and blessed you with a printout. Which was usually a core dump.