> Destin pointed them at NASA SP-287, a document the Apollo engineers wrote and left behind specifically so the next generation wouldn’t have to rediscover everything from scratch. The title is “What Made Apollo a Success.” It has been sitting there, public, for decades. Most of the people in that room had not read it.
> The principle at the center of that document is blunt:
> “Build it simple and then double up on as many components or systems so that if one fails, the other will take over.”
> double up on as many components or systems so that if one fails, the other will take over.”
This is bad advice for a rocket where we are already on the edge of what is even possible. If earth had just a little more gravity it wouldn't be possible to escape our gravity well to a moon. Good engineering is a lot more complex than that simple little advice and a good engineer should already know all the ways that advice is wrong in the real world.
It's not bad advice, it's Great advice. If you're at the leading edge of any technology, you haven't had decades of experience to fall back on to characterize the components involved in the configuration to which they'll be applied. All sorts of new problems cropped up once everything was in space. Clean metal surfaces spontaneously weld, for example.
You obviously have to be well aware of the tyranny of the rocket equation, but you really shouldn't use that as an excuse to try to trick your way around problems in clever ways that are likely to cascade into mission failure and possible cost of the crew at the first little anomaly.
You can't just pull over to the side of the road in aircraft, and space is even more unforgiving. There's nothing to stand on to lever against. Even a slow accumulation of sweat can drown you if you're not careful.
Keep It Simple and Stupid is the bedrock of good engineering.
> The principle at the center of that document is blunt:
> “Build it simple and then double up on as many components or systems so that if one fails, the other will take over.”