Yet software engineers sometimes fail at actually implementing that balance.
> It can be great engineering to make a running shoe that wears out after 2 races, if it wins marathons.
Sure, but it is bad engineering if it fails halfway through the first marathon and injures your runner. See Iowa.
Nobody is complaining about the fact that tradeoffs are made (strawman), what people are complaining about it is that software engineers make tradeoffs unknowingly/don't understand what they are doing.
This is the difference between "we built a bridge that will last two years, because that is all we need" and "To our surprise the bridge already failed after two years, whoops".
> It can be great engineering to make a running shoe that wears out after 2 races, if it wins marathons.
Sure, but it is bad engineering if it fails halfway through the first marathon and injures your runner. See Iowa. Nobody is complaining about the fact that tradeoffs are made (strawman), what people are complaining about it is that software engineers make tradeoffs unknowingly/don't understand what they are doing.
This is the difference between "we built a bridge that will last two years, because that is all we need" and "To our surprise the bridge already failed after two years, whoops".