Timeline for Is premature optimization really the root of all evil?
Current License: CC BY-SA 2.5
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Mar 10, 2015 at 12:33 | comment | added | Olof Forshell | "Planning for optimal performance at design stage is far superior than late optimization of a weak design" and "late optimization provides meagre rewards at a high price" very well put! Probably not true for 97% of all systems produced, but it is for many - disconcertingly many - systems. | |
| Oct 27, 2013 at 3:20 | history | made wiki | Post Made Community Wiki by Michael Shaw | ||
| Jan 26, 2013 at 15:32 | comment | added | Toby Allen | You are quite correct in your case, however for most programmers, they believe they will hit performance issues, but in reality they never will. Many worry about performance when dealing with 1000 of entities, when a basic test on the data would show that performance is fine until they hit 1000000 entities. | |
| May 29, 2011 at 8:37 | history | migrated | from stackoverflow.com (revisions) | ||
| Dec 19, 2008 at 20:58 | comment | added | BCS | Optimize the design at the start, Optimize the code at the end. | |
| Oct 17, 2008 at 10:27 | comment | added | Shane MacLaughlin | It's all about definitions. I take optimization as designing and writing code to perform in an optimal manner. Most here appear to treat it as hacking about with the code once they have found it is not fast or efficient enough. I spend a lot of time optimizing, usually during design. | |
| Oct 17, 2008 at 10:12 | comment | added | Paul de Vrieze | This is certainly correct. I guess that premature optimization is when code is made more complex / hard to understand for unclear benefits, in a way that has only local impact (design has global impact). | |
| Oct 17, 2008 at 8:43 | history | answered | SmacL | CC BY-SA 2.5 |