←back to thread

837 points turrini | 1 comments | | HN request time: 0s | source
Show context
jmward01 ◴[] No.43973868[source]
The goal isn't optimized code, it is utility/value prop. The question then is how do we get the best utility/value given the resources we have. This question often leads to people believing optimization is the right path since it would use fewer resources and therefore the value prop would be higher. I believe they are both right and wrong. For me, almost universally, good optimization ends up simplifying things as it speeds things up. This 'secondary' benefit, to me, is actually the primary benefit. So when considering optimizations I'd argue that performance gains are a potential proxy for simplicity gains in many cases so putting a little more effort into that is almost always worth it. Just make sure you actually are simplifying though.
replies(1): >>43973943 #
1. jayd16 ◴[] No.43973943[source]
You're just replacing one favorite solution with another. Would users want simplicity at the cost of performance? Would they pay more for it? I don't think so.

You're right that the crux of it is that the only thing that matters is pure user value and that it comes in many forms. We're here because development cost and feature set provide the most obvious value.