4 ms·
>Why call it a rocket stage ? Why not just call it exactly what it is - very bad judgement, very poor understanding and simply immature pop cultural choices. Y
by jasode 2y ago
>Why call it a rocket stage ? Why not just call it exactly what it is - very bad judgement, very poor understanding and simply immature pop cultural choices.
You've misunderstood the author's point. It's not about "bad judgement". The extra "rocket stage" is just another metaphor about inevitable "tradeoffs" of simplicity vs complexity.
It's a rewriting of the common adage: Every new solution to an old problem also creates a new set of problems. That's just the tautology part. The question is if you'd rather have the "new problems" instead of the "old problems". That's the cost-benefit analysis part.
E.g. Old car engines carburetors wastes too much gas. New Solution uses more complicated fuel injectors with oxygen sensors and onboard computers to dynamically control the fuel mixture. But now your new solution also created new problems of "oxygen sensors go bad that you have to replace" and "add another supply-chain dependency on computer chips" to assemble completed cars. Ok, got it... we'd still rather have the new problems of replacing oxygen sensors and adding the extra complexity of the ECU computers to gain fuel efficiency.
That's what the author is saying with his last sentence about fully understanding if the extra complexity is worth the cost: >"Maybe it's what you need to get where you want to go, but be clear about the extra weight, operational cost, engineering overheard, mental overhead."
- hnthrow289570 2y agoWe should definitely stop using metaphors involving things we don't understand (rocket design) to explain things we might already understand (software development).
- vitiral 2y agoWe understand almost nothing, so this is like throwing the baby out with the bathwater. I don't think the cost/benefit of a second stage are hard to understand
- hnfong 2y agoI'd be very worried if people who write software for a living actually believe they understand rockets more than software... ... and if not, why the analogy? Aren't analogies used when you want to explain something that people are relatively unfamiliar with, using something they are more familiar with?
- vitiral 2y agoI typically use analogies to make something that is abstract more concrete.