I hate this quote, but less than the "Memory is cheap" mantra..
For "CPU time", if it's a critical path for something with a lot of users and/or where performance is key, the engineer's time is just a fraction.
I hate this quote, but less than the "Memory is cheap" mantra..
For "CPU time", if it's a critical path for something with a lot of users and/or where performance is key, the engineer's time is just a fraction.
Something that used to be precomputed offline can be done in real time. Something that used to work on a small samples can be applied to the whole data set. Something that used to be coarsely approximated can be computed precisely. Something that used to require large clusters of machines can be handled on customers’ client devices. Something that used to be only an end in itself can be used as a building block for a higher-level computation. Etc.
If you require an ROI of 5 years, no interest included, you just created $600k in value over a few weeks.
Scale is key here, but fast software is always a much better user experience than slow stuff as well. With the compiler example, if it takes 1s as opposed to 1h, then users can iterate much more quickly and get a lot of flexibility.
Somehow programmers care about the big O notation, but not when it's about other people's time.