I'm not denying there's better code and worse code in a performance-measurable sense that's written before 'optimization' goes on later in a project.
However, in the real world, we deal with problems. If you have a performance characteristic that's causing issues and you can reproduce it, then you have a problem and you can work on it. The inverse is also true.
Point of premature optimization quote: Most of the time more than a passing / higher-level-architectural thought about performance is not a good idea.
I'm not denying there's better code and worse code in a performance-measurable sense that's written before 'optimization' goes on later in a project.
However, in the real world, we deal with problems. If you have a performance characteristic that's causing issues and you can reproduce it, then you have a problem and you can work on it. The inverse is also true.
Point of premature optimization quote: Most of the time more than a passing / higher-level-architectural thought about performance is not a good idea.