If you want to read about this in fascinating detail, I highly recommend the book "Digital Apollo" by David A. Mindell.
David's book spends a lot of time dwelling on the tension between highly automated systems and the role of the human in them, and the HCI factors of the Apollo missions. They also recap each landing through that lens, including the major changes done to the Lunar Module UI (physical + software) and the landing script/programs for each mission and how things worked out in practice and how it was debriefed after. If you want the insight look at the decision to go for precision landing, how (and how well) it was achieved and how everyone involved felt about it, this is probably your best one-stop go-to.
And for anyone working in embedded UI, or around automation, etc. it's a wondeful mind-sharpener with many lessons in an inspiring applied context.
The Apollo user interface and computer were so state of the art that many of the problems and solutions remain quite similar today. I work in a similar area (cars, with ever-increasing amounts of automation, driver assistance and connectivity) and some of the debates and on-the-job exchanges and meeting notes cited in the book could be straight out of my day job 60 years later with only minute differences. Some of the "Lessons on Software Development"-type docs penned by Apollo engineers in the aftermath of the program (trade-offs of platform approaches and HW abstractions vs. optimization, how to get a handle on quality and testing, etc.) also still read absolutely modern to this day, almost with greater summarizing clarity than what decades of paradigms and jargon have slathered on top.
Thanks for that recommendation. Mendell's other book is not as exciting but they both are the pinnicle of historic technical writing, and yes, this is a sharepining tool for UI, enough to make it required reading.
Of course his interactions with the Apollo engineers is priceless. I worked for one such engineer, and the strain of perfection was great discipline.
David's book spends a lot of time dwelling on the tension between highly automated systems and the role of the human in them, and the HCI factors of the Apollo missions. They also recap each landing through that lens, including the major changes done to the Lunar Module UI (physical + software) and the landing script/programs for each mission and how things worked out in practice and how it was debriefed after. If you want the insight look at the decision to go for precision landing, how (and how well) it was achieved and how everyone involved felt about it, this is probably your best one-stop go-to.
And for anyone working in embedded UI, or around automation, etc. it's a wondeful mind-sharpener with many lessons in an inspiring applied context.
The Apollo user interface and computer were so state of the art that many of the problems and solutions remain quite similar today. I work in a similar area (cars, with ever-increasing amounts of automation, driver assistance and connectivity) and some of the debates and on-the-job exchanges and meeting notes cited in the book could be straight out of my day job 60 years later with only minute differences. Some of the "Lessons on Software Development"-type docs penned by Apollo engineers in the aftermath of the program (trade-offs of platform approaches and HW abstractions vs. optimization, how to get a handle on quality and testing, etc.) also still read absolutely modern to this day, almost with greater summarizing clarity than what decades of paradigms and jargon have slathered on top.