If this is working code that is "production" in nature (i.e. the business depends on it) then re-writing it should be your LAST CONSIDERATION.

Sooner or later you HAVE TO learn to read and work with other people's code, and the sooner you face that music, the better off you and your clients will be.

The book(s) on "refactoring" seems to have been interpreted by many as official license to re-write whatever code you may dislike. While it doesn't say that at all, it's awfully convenient to see it that way.

cheers


>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