I think I'm with Tom on this - "optimisation" can be a moot point before you've even written a line of code!
"Tardy" optimisation is just as big a problem. The key, as you suggest, is probably to test early and test often to ensure you're neither too early or too late with your optimisation. And not to restrict your testing and optimisation to the build phase.
E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).