>>>I don't know how they do things in PA, but, usually developers optimize their code because it adds value to the project. Who do you know that is not optimizing their code?
>>
>>Many people. Optimization - after a minimum level of acceptance has been achieved - is often the last priority in systems. Our systems work at a level that falls within the boundaries of our day-to-day needs, but we have no time to spend optimizing to the nth level as there are 1,157 defects that have nothing to do with optimization that have a higher priority.
>>
>>Just my dollar's worth.
>
>I am aware that some BIG corporate IT departments are releasing work products that are barely alpha (mostly untested). ALong the the lines "Just put it out there and let the end users debug it" That is a fact of life.
>
>But little project guys, that don't have the luxury of a captive audience, ie: their boss (IT's) is the same as the users', have to get it as right as it can be before it's delivered. The user's first impression can sometimes make or break the project! Some (mostly independent contractors and small custome shops) depend on word of mouth and reputation to keep them gigs a flowing. They have have to pay attention - next month's grocery sack may depend on it!
>
>That being said, a little code snippet, for the sake of clarification <g>, has little or no reason for not being optimized.

But none of those qualifiers were in your previous posts. We are not "big," but rather "busy." I think the fact of the matter is that most developers work for someone - permanent or contracting - and are not "little project guys." There are always exceptions, but your specific logic really wasn't applicable in general.