There's something amazing about carrying around your dot-matrix printed source code in a roller suitcase. The only thing that says "stable release" more than printing it out on hundreds of pages of paper is launching the computer running the code into space with no hope of doing an update.
There's a link to the source code on GitHub[0], is that not the full source though? Just searching for a comment like 'hello there' from the photo[1] doesn't seem to exist in the repo.<p>[0] <a href="https://github.com/chrislgarry/Apollo-11" rel="nofollow">https://github.com/chrislgarry/Apollo-11</a><p>[1] <a href="https://hackadaycom.files.wordpress.com/2016/07/apollo-sourcecode-example-wb.jpg" rel="nofollow">https://hackadaycom.files.wordpress.com/2016/07/apollo-sourc...</a>
If you enjoy this, you might also enjoy a DIY Apollo Guidance Computer build by John Pultorak [1]:<p>"John Pultorak created a working reproduction of the Apollo Guidance Computer (AGC), wrote a complete manual that will allow you to build your own Apollo flight computer clone and released it in the public domain."<p>[1]: <a href="http://www.galaxiki.org/web/main/_blog/all/build-your-own-nasa-apollo-landing-computer-no-kidding.shtml" rel="nofollow">http://www.galaxiki.org/web/main/_blog/all/build-your-own-na...</a>
The I/O on the diagram blows your mind, I wish the projects I worked on had outputs like Decent Engine<p>My career choices really suck, should have joined NASA or SpaceX :-)
There's mention of interpreted sections in the code. Do you know if it was possible to manually enter interpreted code to have it ran by the system afterward - or even program some of software by hand (being dictated hex) in case something unexpected occurring during the mission warranted it?