5 ms·
The reasoning behind discouraging premature optimization makes no distinction between "micro optimizations" and any other kind, the purpose of this guidance is
by root_axis 4y ago
The reasoning behind discouraging premature optimization makes no distinction between "micro optimizations" and any other kind, the purpose of this guidance is to minimize wasting time building unnecessarily complex solutions based on untested performance assumptions.
- hsn915 4y agoIt does not generalize from low level micro optimizations to high level sensible system design. At the low levels you really have no idea where the performance bottle necks are without profiling and getting actual numbers to work with. At the high level you pretty much have a clear idea of what roughly the system is supposed to do and what performance characteristics you want.
- gonzo41 4y agoI think this comes down to a level of experience. If you're writing and enterprise app and lean back in your chair and start to think about speeding things up with loop unrolling and avx instruction sets then you're doing the premature optimization thing. But trying to limit large nested loops is easy fruit that doesn't take much effort to pick.