If instead of measuring the benchmark of a specific optimized code against a non-optimized code we instead measure the time when the user gets their answer in m

If instead of measuring the benchmark of a specific optimized code against a non-optimized code we instead measure the time when the user gets their answer in many cases the non-optimized code will be several months faster. Why? Because it takes time to do optimizations and I can ship the non-optimized sooner. Similarly we can then look at an iterated design and realize the optimized code is frequently going to be harder to refactor or understand (a precondition of refactoring). So now the time to when a customer gets their answer is delayed again. Optimization step comes long after clean code. Clean code is most useful in the first 2 of the typical 3 steps[1] 1. Make it work (iterations of what working even means) 2. Make it right (iterations of what right even means) 3. Make it fast. [1]:https://wiki.c2.com/?MakeItWorkMakeItRightMakeItFast https://wiki.c2.com/?MakeItWorkMakeItRightMakeItFast