>I agree with you, George, especially in this day of very cheap gigahertz CPUs.
>Worrying about "fast" need only really be limited I/O in my opinion. Of course there can be exceptions, but they really would be exceptions.
>
Jim,

In my mind, the biggest problem is that people that "throw code" at a problem don't realize that in doing so, they may not have achieved any performance gain with the more or less in-line approach.

They like to think that not only does the code execute faster, but it takes less time.

Studies have shown that while those type of solutions may be marginally faster, the overall time to implement is actually about 10% slower. Further, the support and modification time is nearly 10 times what it would be if the code was written for correctness and quality.