Re: What makes a programmer look low level

2005-05-11 Thread Michael Bramwell
I agree, that is complete overkill, it is much more readible to use commenting: // some variables with dodgy names a = 1; b = 2; Where I work we don't use cfform at all as it messes with our javascript validation functions. As for cfinsert and the like, I have never used these as

RE: What makes a programmer look low level

2005-05-11 Thread Glenn Saunders
At 01:52 PM 5/9/2005, you wrote: >Is it just me, or do the comments other developers leave throughout their >code mostly get in the way of just reading the raw code? Having read through >all kinds of existing code, I much prefer to have everything scoped and the >code arranged in a consistent, logi

Re: What makes a programmer look low level

2005-05-11 Thread Glenn Saunders
At 01:14 PM 5/9/2005, you wrote: >That reminds me of one...Select * in SQL statements...thats a really >big PITA and a sign of a beginner or a lazy coder... I guess that would make me a lazy coder. I don't think this is always the case if your application is evolving a lot. Remember, you never r

Re: What makes a programmer look low level

2005-05-11 Thread Glenn Saunders
At 01:11 PM 5/9/2005, you wrote: >along with -- up until now -- >cfform. What do you have against CFFORM? ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting h

Re: What makes a programmer look low level

2005-05-11 Thread Glenn Saunders
At 01:10 PM 5/9/2005, you wrote: >Like I said I knew people would disagree, and I understand that which >is why I scope everything b/c I dislike being a black sheep :) But >I'll ask why are people so adamant about it? Because CF has to interrogate memory on unscoped variables based on a predefine

Re: What makes a programmer look low level

2005-05-11 Thread Glenn Saunders
At 12:55 PM 5/9/2005, you wrote: >So me scoping myQuery.varname is essential in a query="myQuery"> block? I disagree but I know people think I never do that unless there is a variable name collision, which I then try to avoid anyway. I also sometimes don't use variables. just to avoid extra keys

Re: What makes a programmer look low level

2005-05-11 Thread Glenn Saunders
At 11:14 AM 5/9/2005, you wrote: > > good: mycart[1].productname > > good: mycart[1]["productname"] > > bad: mycart[1][1] (not-descriptive) > > bad: mycart[1][productname] (overcomplicated) I have also seen cases of pseudoarrays that could be real arrays: a_1 a_2 a_3 vs. a[1] a[2

Re: What makes a programmer look low level

2005-05-11 Thread Aaron Rouse
These two I seem to never come across, do many people come across code using them? On 5/11/05, Glenn Saunders <[EMAIL PROTECTED]> wrote: > > > > I'm also not too fond of code that uses CFINSERT and CFUPDATE usage > instead > of calling a proc or doing it via cfquery. > > > ~~

Re: What makes a programmer look low level

2005-05-11 Thread Glenn Saunders
At 10:50 AM 5/9/2005, you wrote: >I am sure you can, however I am referring to the blatantly obvious places it >is not needed and does nothing more than slow down a page from loading. It >shows that someone does not fully understand what I would consider basic SQL >and CFM skills. I'm also not too

Re: What makes a programmer look low level

2005-05-11 Thread Glenn Saunders
At 10:47 AM 5/9/2005, you wrote: >I can see places where this is needed If the join is across servers, sure. If the join was expensive enough and you were doing a paged view then you could run one query per page with a valuelist of the foreign keys rather than doing a round trip to the db on ev

Re: What makes a programmer look low level

2005-05-11 Thread Glenn Saunders
At 10:33 AM 5/9/2005, you wrote: I have met some developers that are very talented (I'd >consider them "Senior" level developers based on skill alone) who happen >to have poor syntax/code style habits. Did you explain to them the right way to do it? If so, did they change? If they didn't, that