>>Folks:
>>
>>Is it just me, or do you people think it's easier/faster to
>>just write your own code than to try and figure out
>>what another programmer is doing in his/her programs?
>>
>>I'm sure all of us here are well aware of "programming style."
>>I've seen "code that matches my way of thinking," and
>>"code that could _easily_ win 'The Obfuscated C programming
>>Contest' -- HANDS DOWN! :^) -- held on the Usenet every year.
>>
>>Fortunately, a friend of mine and I have replaced some dewd that
>>seems to think like we do, so reading his code isn't really all that
>>difficult; however, it is very time consuming! What do you people
>>think? Anyone else out there been/going through this? :^)
>>
>>Randall
>
>When it come to other peoples code, I follow a straight and simple principle. "If it not broken, don't fix it." Generally, there is a reason the the code was written the way it was.

I have only seen that from the better developers. The average ones seem to have "it was the only way I knew how to do it" as their answer.


> If the coder was on the ball, they would have added comment to describe why the code is the way it is. But, developers are generally more interested in coding then documenting.
>
>My suggestion is leave the original code the way it is and clone it for the next version of the application. You will then have a foundation to use as reference.
>
>Remimber these three words. Save, Backup, and Comment.
>
>Best of luck.

Agreed.