dragonchild,
I agree with your sentiment but not the conclusions some might draw from it. It could be argued that what you are saying is tantamount to

It does not matter how inefficient the code you write is. It is not necessary to understand the complexities of algorithms, data structures, profiling, or benchmarking. It is only important to write code as fast as possible that does the job because CPU time is less expensive.

In my opinion, it is much better to teach someone to think for themself in determining when and where to spend their time (optimizing or not) than to give them more dogma to follow blindly and mantras to chant to bring more into the fold.

Update: s/sloppy/inefficient/ as sloppy has meanings other than I intended. I asked in the CB if the tone of this message seemed inflamatory, which was not my intention. A couple said no and one said yes. I apologize if this is offensive.