Tales from the lunar module guidance computer (2004)
doneyles.com
doneyles.com
I'd also love to see a book by Allan Klumpp. He wrote the ultimate mic drop review on Amazon: http://www.amazon.com/gp/review/R3VJW144Y9YDBQ?ref_=glimp_1r...
After stating that he hates the book, he writes, "I have mastered six programming languages from language reference manuals, and my software has been used at five planets and the moon, so I speak advisedly." Ouch.
On the other hand, the "struggling for seven years" part suggests that he might not be a transdimensional supergenius, or at least might not be brilliant about allocating his time. At some point you'd ordinarily just chuck a bad book in the trash.
Does anyone else know of similar accounts of early spaceflights? I'd love to know if the audio from the radio is available too.
Sometimes the rate of technological advance is just staggering.
[1] https://www.amazon.com/Dream-Machine-Licklider-Revolution-Co...
There's a full description in the article, though it's buried a bit far down. Here's a snippet for grep-ability:
if a low-priority job was executing and a high-priority job was scheduled, the low-priority job was suspended while the higher-priority job executed.Sleep-and-assume programming is the bane of automation. Ideally, the software people should have gotten the hardware people to install some kind of sensor to detect the right condition, but I guess it was either limited by what could actually be done with the hardware, or maybe they didn't have enough influence to get the design changed...
I also think of this as related to the second system syndrome - Apollo was the first system for a lot of these engineers, and doing lots of things for the first time ever. People were bold and cautious at the same time. The Space Shuttle was the second system - an way over engineered system that did not reach the targets it was designed for, and was successful only through large amounts of money being thrown at the problem.