Performance Optimization and all that

There is an ongoing discussion (cross-references, etc) regarding Performance Optimization. Sam cited the very recent articles in MSDN (excellent ones I might add) but in sharp contrast James Robertson proffers his views. I did respond with a minor (perhaps an inconsequential one) that's excerpted here:

'Unmaintainable code' is a relative term that can be balanced by good documentation. Performance-oriented code have more thought into it and if it conforms to the requirements (including documentation) then all the more power to it.

There was an additional response regarding the issue in the use of 'algorithms' - who can forget that 'Data Structures + Algorithms = Computer Programs' ? I certainly standby my above statement and would like to elaborate that the development environment also plays a decisive role - if you code here and here then your peers will deeply delve (& appreciate) your optimization. Such freedom to developers goes a long way and not merely in terms of productivity. Whereas, if you develop here and here then as long as it meets the requirements and the code is documented and you get it done yesterday then it's okey-dokey.