flyingbarron

oops, sorry - submitted wrong link :(

Fantastic story! One of the fascinating things about this are the parallels to Apollo 12 - Lightning strike / Power surge lead to a total loss of telemetry which raised the specter of losing the entire mission - and a similar resolution when telemetry was restored!

I've written a bit about it myself - https://flyingbarron.medium.com/lightning-strikes-92482387ca...

For the last three years I've been writing a series of articles about lessons modern software operations can learn from the work of NASA's astronauts, engineers, managers, and scientists. I've been calling them "Lessons from the Lunar Landings". Today, I've published an index of sorts and I'd like to share it with you, in hope that it's of interest.

Still doesn't explain why "Day" and not "Phase" or "Stage" or "Level" or "Period"

I think I covered the basic explanation in my article as well as dzone and gitlab did in theirs.

:D

I honestly don't know.

Just to clarify, the term "Day-2" isn't from NASA, it's a universal engineering term - which mostly happens on Earth ;)

I'm guessing it's just a planning term - like D-Day :shrugs:

I think it emphasizes the importance of the results - it's for everyone, not just scientific types.

Back in 1964, President Lyndon Johnson "expressed interest" in the first close-up pictures NASA got from the Moon on Ranger 7. The freshly developed images were loaded onto a plane and the President got a private briefing with the head of NASA on the very same day. (sorry, I don't think I can link the picture) https://history.nasa.gov/SP-4210/pages/Ch_18.htm

I'm pretty sure that if there was any bad news they'd be managing expectations.

This is the quiet of confidence, I think :)