In the past, others have reported that SpaceX execs have stated that one of SpaceX's engineering goals is to create a process "where software could be installed from head at any time and used to immediately fly a mission."
"The most important point stressed was the deeper they got into developing their process, the more focus they spent on building and verifying their simulators and test suite and the less emphasis they put on writing the actual code."
So what I'm wondering is: Do they have a faster way to verify their simulators other than good old fashioned traditional code reviews and just blowing rockets up more often than the average joe, or does that pretty much cover it?
Anyone knowledgable in the subject care to chime in?
[0] https://www.linkedin.com/pulse/spacex-bringing-agile-bdd-final-frontier-timothy-brandt (a little kool-aidish ref, sorry)