story
When a customer presses a button to book a taxi ride, they don't care whether the underlying database query takes O(log N) or O(N^2). As long as the price is good and they get a response within 3-5 seconds, they're cool.
This works for the absolute majority of real-world projects. Technical excellence has very little impact on the revenue, compared to other factors (product/market fit), so people making business decisions don't care about it.
>That's great. Then they should actually stick with it i.e. reward the 1 that's been contributing rather than gamble on something that might not work.
Business is always a gamble. You don't know how the market will take your product before you launch it. You don't know what the competitors will do, how the sentiment will change, let alone global events like the COVID money printing followed by an interest rate squeeze. It's like you are trying to navigate a ship in a storm, and the mechanic keeps telling you how he can shove coal 5x faster than others and hence needs to be paid more. Except, you never need it that fast, and need to have 2 onboard anyway, in case one gets sick.
