Timeline for Is it always wrong to optimize before profiling?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Oct 25, 2016 at 18:17 | history | suggested | SusanW | CC BY-SA 3.0 |
Fixed typo!
|
| Oct 25, 2016 at 17:59 | review | Suggested edits | |||
| S Oct 25, 2016 at 18:17 | |||||
| Apr 1, 2011 at 15:56 | comment | added | David Thornley | @CodeninjaTim: Not to mention that, if you're a contractor, presenting the speedup results is a nice way of showing those who have hired you that you haven't been wasting time with that code fiddling. | |
| Mar 31, 2011 at 15:46 | comment | added | Cercerilla | Measuring the performance improvement is a good point. There are certainly cases where I know a given optimization will speed things up, but I make the change before gathering before and after data to see how much of an improvement it is. | |
| Mar 31, 2011 at 14:57 | history | answered | Berin Loritsch | CC BY-SA 2.5 |