At 01:25 PM 5/9/2005, you wrote:
How about we look at what makes a programmer look low level and work our
way up. Two things that come right to mind are:
1. Improper use of pound signs in evaluation zones
2. Improper usage of IF clauses (not using short circuited Boolean evaluation)
A few
This could be purposely done and part of someones style. I always do the
cfif IsDefined() AND ... method but have seen the other route taken from
rather knowledgable people. At what point do you decide it would be easier
to follow some nested if's over one single long if statement. I can not
Not scoping variables. Both, in regular templates (Is this a form
variable, a URL variable, a local variable, etc.. ) and in Functions / CFCs
(where improper scoping is more likely to have adverse side affects).
I think scoping variables makes code easier to read but to me scoping
every
At 01:25 PM 5/9/2005, you wrote:
How about we look at what makes a programmer look low
level and work our
way up. Two things that come right to mind are:
1. Improper use of pound signs in evaluation zones
2. Improper usage of IF clauses (not using short circuited
Boolean evaluation)
A few
At 03:13 PM 5/9/2005, you wrote:
At 01:25 PM 5/9/2005, you wrote:
How about we look at what makes a programmer look low
level and work our
way up. Two things that come right to mind are:
1. Improper use of pound signs in evaluation zones
2. Improper usage of IF clauses (not using short
How would you spot these in a code sample? :P
cfif parameterExists...
- Jim
S. Isaac Dealey wrote:
How would you spot these in a code sample? :P
1. An unwillingness to learn
2. Believing that they have no room for improvement
3. Blindly following the advice of some so-called
Credible
it's worth noting that none of these are easy to determine in an
interview. Some people are great developers who have poor interview
skills, which makes it entirely possible to mistake these qualities (or
lack thereof).
~Simon
Simon Horwith
CIO, AboutWeb - http://www.aboutweb.com
I've got to disagree - I prefix every variable I reference and can only
fault those who don't. I think the reasons for this have already been
discussed.
~Simon
Simon Horwith
CIO, AboutWeb - http://www.aboutweb.com
Editor-in-Chief, ColdFusion Developers Journal
Member of Team Macromedia
Nice! :) That one actually got a literal laugh out loud on this end.
:)
How would you spot these in a code sample? :P
cfif parameterExists...
- Jim
S. Isaac Dealey wrote:
How would you spot these in a code sample? :P
1. An unwillingness to learn
2. Believing that they have no room
So me scoping myQuery.varname is essential in a cfoutput
query=myQuery block? I disagree but I know people think
differently... I do agree with the url. or form. or cookie . though in
many cases it could be coming from different places so scoping those
are good. If you understand your current
What makes a programmer look low level is:
1. Not predefining variable for later use at start of code file or in a
universal inclusion. Really, I think people should be held accountable to write
out in documentation every variable used along with every set of data whether
originating in a
not only do I adamantly believe that inside of a CFOUTPUT query= loop
should you prefix the column names with the query name, but I also scope
the variable (cfoutput query=variables.qMyQuery.).
~Simon
Simon Horwith
CIO, AboutWeb - http://www.aboutweb.com
Editor-in-Chief, ColdFusion
Easy. You find some code they wrote three years ago. Then you find some code
they wrote recently. Use brain to determine how much they've learned.
- Original Message -
From: S. Isaac Dealey [EMAIL PROTECTED]
Date: Monday, May 9, 2005 1:32 pm
Subject: Re: What makes a programmer look
I tend to scope these, it is not out of worry of me not knowing what I am
referencing or even of someone else coming in and not knowing. I think it is
more of just out of habbit and it just gets typed. I do know at one time I
came across a prior developers work who would be in a cfoutput
What makes a programmer look low level is:
1. Not predefining variable for later use at start of code
file or in a universal inclusion. Really, I think people
should be held accountable to write out in documentation
every variable used along with every set of data whether
originating in a
Code encapsulation is CS101 concept. If someone is not understanding
encapsulation, then they are a novice programmer.
Whether they are a novice CF Developer or not may be open to
interpretation, since many CF Developers are not programmers by trade.
At 03:50 PM 5/9/2005, you wrote:
I
-Original Message-
From: Simon Horwith [mailto:[EMAIL PROTECTED]
I'd love to know how ou find code that an applicant wrote 3 years
ago.
Contributions to OSS?
--
Damien McKenna - Web Developer - [EMAIL PROTECTED]
The Limu Company - http://www.thelimucompany.com/ - 407-804-1014
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?
Adam H
On 5/9/05, Simon Horwith [EMAIL PROTECTED] wrote:
not only do I adamantly believe that inside of a
Oh yeah I forgot another short sighted new programmer
annoyance I hold is:
Complex code that isn't tabbed or seperated like in case
of a query with 100 fields running a big comma list versus
putting a carriage return after each field name follwed by
a comma.
Makes debugging a pain since
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 completely understand readability but I would like to think my
comments will help even the novice of developers understand where my
variables are...but I see that...and
If this is a matter of finding the right candidate, I'd be most interested in
what they have done. How many projects? Where are the projects online to run
through the paces? How similar is anything they have done to anything you are
doing? Are they familiar with your industry? With your
I agree that if we're generalizing, any developer that doesn't
encapslate code is a poor developer (novice or otherwise) but CF, as you
say, has many developers that aren't developers by trade at all. CF
Applications are often times so simple that to call them an
application may seem like a
I've seen pages that reference a variable like #user_id# inside and
outside of a query loop - and the page accepts a url parameter and form
field with this name AS WELL as having a query containing a column with
that name. Not specifying where the variable came from makes the code
much more
Adam Haskell wrote:
I think scoping variables makes code easier to read but to me scoping
every single vaible tells me you either 1) don;t trust your code or 2)
don't understand how scope is working in your current situation which
would imply a lower level of skill. I know most poeple will
When you say Structure are you talking about code formatting, or
something different? My impression is that you are referring to code
formatting however structure could mean different things, so...
I'd rather see comments than formatted code. I can read unformatted
code, or format it as
Both, but mostly code formatting. The architecture, if applied to framework
properly, can make it that much more easy to pick everything up at a glance.
But for our purposes here, lets just say formatting. The problem with
referring to documentation that tells you what the code or app does is that
I generally put form and urls into a My structure. THen I do
my.variableName..but I suppose to appease some I should be doing
variables.my.variableName ;)
Adam H
On 5/9/05, Jeffry Houser [EMAIL PROTECTED] wrote:
If a page can be accessed via both url requests and form posts how
does one
What I have seen some do is put URL and FORM into the REQUEST scope and then
reference that scope.
On 5/9/05, Jeffry Houser [EMAIL PROTECTED] wrote:
If a page can be accessed via both url requests and form posts how
does one handle a variable that may be in either scope? Do ya'll use a
You can ask the applicant, ask a company the applicant has
worked for, see if they have any open source projects,
etc...
I never have problems getting code samples from
applicants, even code that's a few years old. Most people
are quite proud of what they've worked on, regardless of
what
The length of time someone has worked is not necessarily an indicator of their
experience level. Even someone who is a recent graduate could have written
something in an intership position or (I hope) classes they have taken. Point
being, I have never met anyone applying for even the most
Good documentation should show you how it does work.
I find it hard to imagine a point where code documentation detracts from
code readability, which is what your original complaint was.
At 05:43 PM 5/9/2005, you wrote:
Both, but mostly code formatting. The architecture, if applied to
I agree. My point about having at least 3 years of experience wasn't
that it is an indicator of their level of experience... just that anyone
who is applying for an entry level position and has 3 years of
experience, is most likely not very sharp.
~Simon
Simon Horwith
CIO, AboutWeb -
1. Not predefining variable for later use at
start of code file or in a universal inclusion.
I'll disagree here and say this is a matter of style, not skill. This makes
sense to do in an environment where multiple developers will be working on
the same code-base all the time, but for smaller
Not all documentation is good; in fact, most is bad (in my experience.) It
saves time to go right to the code to see how it actually works. When you're
reading through the lines, it seems easier and more readable without
comments interrupting your train of thought. Doesn't take much imagination,
34 matches
Mail list logo
