IMHO I think that some succinct code is harder to read then more long-winded, e.g complicated IIF() instead of If .. ELse ... Endif, the use of !EOF() instead of Not EOF(), abbrev. of VFP commands, petty savings in typing (esp. as one can use global replace for these expressions later - as I often do to othe3r's code to make it readable), using crap short meaningless var names, bad indentation and, worst of all, momnolithic code with 20-page-long Do while loops with several inside them and nested Ifs to boot.

Personally speaking, IMHO, I think that I have the neatest, most readable, well laid-out code of anyone's I've ever read, and I take great care to make it so.

But maybe it's only MY mental map that sees it that way.


>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