A typical Molecular software development kit comprised:
When you were ready to try out your code, you used the OP utility to load it in octal. Beginners would first write all the octal onto the coding sheets but after a little practice this was only useful occasionally, when constructing subroutine control words for example. Later alterations would be clearly marked with an asterisk in the margin, to be rubbed out after loading.
No matter how carefully you checked your code, there was always a fair chance it would crash first time! So you always warned anyone else on the machine before you ran a test, waited a few seconds, then let it rip. By the 1990's I often worked remotely, using a 300bps modem connection to load whole new programs directly onto users' live systems. This would only be done after everyone had gone home; when the time came to run the new code it could be a little nerve-racking knowing that any crash could not be dealt with until the next morning!
Completed coding sheets were stored in Foolscap Lever Arch files. A complete set of documentation for one client could run to five hefty files.