: Wednesday, June 16, 2004 5:50 PM
To: CF-Jobs-Talk
Subject: Re: was a tricky situation
When I was working at Rice University a few years back there were numerous
code examples that match what you just gave.It was horrible to go in
behind the developers who had made those systems and try to debug
than anything else.
Larry
-Original Message-
From: Aaron Rouse [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 5:50 PM
To: CF-Jobs-Talk
Subject: Re: was a tricky situation
When I was working at Rice University a few years back there were numerous
code examples
that some people develop pages strictly for
job security. The maintenance on the old page was ugly.
larry
-Original Message-
From: Aaron Rouse [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 17, 2004 10:31 AM
To: CF-Jobs-Talk
Subject: RE: was a tricky situation
I actually just remember even
I take umbrage at the term demented fuseboxer coder
ducking
_
From: Lyons, Larry [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 17, 2004 10:31 AM
To: CF-Jobs-Talk
Subject: RE: was a tricky situation
This week I am dealing with a page that makes at least 8 database calls all
the same
quote
Just goes to show, that there is a right way and a wrong way to write
code
/quote
I would modify that slightly, making it more correct but probably with less impact:...there are many right ways, and even more wrong ways to write code...
Ian
Confidentiality Notice:This message
I used to work for a healthcare e-Learning firm. We had a CF polling
application
that was built-in to a Web conferencing system.The polling application
would
present all the users in the Web conference with an HTML form and allow them
to answer a series of questions.Their answers were submitted to
so here's an example. Its not wrong just hard to read
all forms post to a page called process.cfm which does a cfif on the name of the submit button.
after a bit he found that the process page was getting too long so now there are pages called process2.cfm process3.cfm and so on.
Are joins
