4 ms·
I would contend that in the successful cases where you are optimizing from the beginning, you are actually doing a two stage process, one design stage where you
by kbenson 12y ago
I would contend that in the successful cases where you are optimizing from the beginning, you are actually doing a two stage process, one design stage where you figure out what you need, and another where you figure out how to do that efficiently and fast. To some degree, it's semantics (when is optimization not design related?), but my point was that optimization before nailing down the requirements for that component is what leads to problems. I think that's the premature in premature optimization, when you spend time optimizing something you aren't sure will even survive a later point in the design stage.
- SomeCallMeTim 12y ago> I think that's the premature in premature optimization, when you spend time optimizing something you aren't sure will even survive a later point in the design stage. That's true enough, though it doesn't seem to be the original point, since the context refers to optimizing parts of the code that aren't taking most of the time. Which is a danger, but I think the danger is in wasting time on such optimizations, either up front or through increased complexity.