There is that as well. :) One time, I read an article that suggested that you name your variables as something that means something, but not defining the variable.
For example.. <cfset Santa=39> <cfset Gandalf=30> <cfset Raptor=Gandalf+Santa> Really mess with the future developers heads that way. :) But I like to think that what goes around comes around. So I don't do this. On Fri, Jan 14, 2011 at 2:26 PM, Joel Polsky <[email protected]> wrote: > > LOL! Or it can be considered job security - for if they ever want to be able > to decifer your code - best not let you go! > > On Fri, Jan 14, 2011 at 4:05 PM, Phillip Vector > <[email protected]>wrote: > >> >> hhehehe. My mentor once told me, "When you code, pretend that the next >> developer after you (and there will be) is a crazed killer who has >> your home address and a picture of you". After he told me that, my >> code got ALLOT more readable. :) >> >> On Fri, Jan 14, 2011 at 1:00 PM, Joel Polsky <[email protected]> >> wrote: >> > >> > Put your self in the >> > next developer's shoes - could *YOU* figure it out if you had no >> knowledge >> > of what the database was for? >> >> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-newbie/message.cfm/messageid:5207 Subscription: http://www.houseoffusion.com/groups/cf-newbie/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-newbie/unsubscribe.cfm
