Timeline for Is micro-optimisation important when coding?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 9, 2011 at 15:59 | comment | added | back2dos | @Nim: Point taken ;) | |
| Aug 9, 2011 at 14:33 | history | edited | Carl Manaster | CC BY-SA 3.0 | typo |
| Aug 9, 2011 at 14:24 | comment | added | Nim | I generally agree - except for one line, I contend that "every idiot thinks they can micro-optimize"... ;) | |
| Aug 9, 2011 at 9:45 | comment | added | Marco | The best answer to me was found, remarkably, in the Bugzilla Developer's Guide: "If you're trying to be clever instead of trying to be readable, then maybe you're trying to make things "faster?" If so, just remember: don't solve a problem before you know it exists. If you don't know (by actual, detailed tests) that your code is slow, don't worry about making it "faster." This isn't just limited to optimization--many programmers are constantly solving problems that nobody has ever experienced. Don't do that." bugzilla.org/docs/developer.html#general | |
| S Aug 8, 2011 at 17:39 | history | answered | back2dos | CC BY-SA 3.0 | |
| S Aug 8, 2011 at 17:39 | history | made wiki | Post Made Community Wiki by back2dos |