RE: was a tricky situation

2004-06-17 Thread Aaron West
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

RE: was a tricky situation

2004-06-17 Thread Ian Skinner
Just goes to show, that there is a right way and a wrong way to write code 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 including any

RE: was a tricky situation

2004-06-17 Thread Aaron West
ED]   Sent: Thursday, June 17, 2004 10:05 AM   To: CF-Jobs-Talk   Subject: RE: was a tricky situation   I did a report here about 2-3 years ago and it uses a rather   "complicated" single query or did when I wrote the report.  It was nice   and fast to run and everything was there as per spe

RE: was a tricky situation

2004-06-17 Thread Lyons, Larry
imply looked at the thing and made a case for rebuilding the entire site. larry -Original Message- From: Aaron Rouse [mailto:[EMAIL PROTECTED] Sent: Thursday, June 17, 2004 11:05 AM To: CF-Jobs-Talk Subject: RE: was a tricky situation I did a report here about 2-3 years ago and it uses a r

RE: was a tricky situation

2004-06-17 Thread Aaron Rouse
on, without naming name > that > > is. AS far as I can figure at least some of the time an approach, the app > > was written more to provide job security than anything else. > > > > Larry > >   > > -Original Message- > > From: Aaron Rouse [m

RE: was a tricky situation

2004-06-17 Thread Jeffry Houser
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, no caching etc, with more includes that a demented fusebox coder >would use.  I ended up rewriting the page. Now it

RE: was a tricky situation

2004-06-17 Thread Lyons, Larry
Come now Sandy, everyone knows you only get demented on the weekends. larry -Original Message- From: Sandy Clark [mailto:[EMAIL PROTECTED] Sent: Thursday, June 17, 2004 10:43 AM To: CF-Jobs-Talk Subject: RE: was a tricky situation I take umbrage at the term "demented fuseboxer

RE: was a tricky situation

2004-06-17 Thread Sandy Clark
I take umbrage at the term "demented fuseboxer coder"     _   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 th

RE: was a tricky situation

2004-06-17 Thread Lyons, Larry
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

RE: was a tricky situation

2004-06-17 Thread Aaron Rouse
nything 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 the

RE: was a tricky situation

2004-06-17 Thread Jeffry Houser
gt;was written more to provide job security 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 wo

RE: was a tricky situation

2004-06-17 Thread Lyons, Larry
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 match what you just gave.  It was horrible to go in behind the developers who had made those systems and try to

Re: was a tricky situation

2004-06-16 Thread Joshua O'Connor-Rose
That's pretty much the advice I was looking for originaly. -Joshua [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Re: was a tricky situation

2004-06-16 Thread Aaron Rouse
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 a problem.  They were always very unaccepting of change in coding methods or much of an

Re: was a tricky situation

2004-06-16 Thread Joshua O'Connor-Rose
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 cumbe

Re: was a tricky situation

2004-06-16 Thread Aaron Rouse
Just read the post on cf-talk, we have one of those people here as well.  I try to just not think too hard on it, because if not then I get rather irritated and that helps matters none. Snipe - On Wed, 16 Jun 2004, Jeffry Houser wrote: > At 04:26 PM 6/16/2004, you wrote: > >moved the conversati

Re: was a tricky situation

2004-06-16 Thread Jeffry Houser
At 04:26 PM 6/16/2004, you wrote: >moved the conversation here and this reply is for Mr. Houser > >Senior meant senior developer not a manager.   Oh...   I work with one of those too. -- Jeffry Houser, Web Developer, Writer, Songwriter, Recording Engineer -- AIM: Reboog711  | Phone: 1-203-379-07

was a tricky situation

2004-06-16 Thread Joshua O'Connor-Rose
moved the conversation here and this reply is for Mr. Houser Senior meant senior developer not a manager. Again he's the golden developer boy (but he realy needs to go to class) I had trouble posting because I can't seem to change my email address on the cf-talk lists, I didn't know what sort of