Timeline for Is premature optimization always bad?
Current License: CC BY-SA 2.5
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 15, 2012 at 13:27 | comment | added | Doc Brown | There is a form of optimizing prematurely which does not seem to reduce readability at first hand, but will produce issues on the long term and so is very bad: introducing redundant variables. Though the code seems to be readable, you run into problems when trying to change or extend it later, when there is more than "one single source of truth". | |
| May 11, 2011 at 13:17 | comment | added | Malfist | optimizing premature is not only bad if it reduces readability. If I spend two days optimizing an obscure part of my program that is hardly ever used, I've wasted my employer's money. You should always profile to figure out where you need to optimize before you optimize. | |
| Feb 8, 2011 at 11:36 | comment | added | glenatron | If only there was somewhere you could post some examples and get feedback on how readable or otherwise they actually are... codereview.stackexchange.com | |
| Feb 8, 2011 at 3:45 | comment | added | MattyD | That sounds like a good plan! Hopefully I can get back to the roots and stop being a tool ;) | |
| Feb 8, 2011 at 3:43 | comment | added | GavinH | If you are concerned, I'd go through parts of the code you know to be a bit hairy and add some explanatory comments. Not line-by-line 'create a new object' or 'add 4 to x' comments, but a few paragraphs to give an overview of what's happening. | |
| Feb 8, 2011 at 3:36 | vote | accept | MattyD | ||
| Feb 8, 2011 at 3:33 | comment | added | MattyD | Well I'd be the only person viewing the actual code, just my concern was if I get replaces or another team member it could cause issues. | |
| Feb 8, 2011 at 3:28 | history | answered | GavinH | CC BY-SA 2.5 |