If your code doesn't do what you want it to do, you have no business optimizing it.
Ah, you haven't been out of junior class yet.
If I lose more sales because of performance issues than I lose because of bugs, or missing (edge) cases, performance *is* more important than making it do what I want. Or, if the boost in sales of cutting corners is more than the lost in sales because of the corners being cut, I have all the business case I need to optimize it.
To give an example, if I use software that calculates an "optimal" route for me to deliver packages to 40 customers, I rather have a slightly optimal route that's ready by the time I start driving, then that I've to wait another few years just to find out I could save a few seconds from my trip.
Seasoned programmers know when a solution is "good enough" and performance becomes as important (or even more important) as being "perfect".
In reply to Re: The Rules of Optimization Club
by JavaFan
in thread The Rules of Optimization Club
by petdance
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |