It depends on three things:
1. Who will be maintaining the code?
2. How many people are working on the site?
3. Preference.
It's a good habit worth getting into, because I've found as I work on
larger and larger sites, that a consistent naming convention is nice even
if I'm the only one who sees the code. It also helps when I come back to
old code to "pick up where I left off."
I also give extra points to a job candidate's code if it follows a
consistent, easy-to-understand naming convention.
Sharon
At 10:42 AM 10/23/2000 -0600, Erika Foster wrote:
>Do most of you use some kind of naming convention for your backend table
>names, queries, fieldnames, etc. I'm curious as to what the benefit is of
>using , say, the Leszynski/Reddick naming convention for a backend that the
>client never really sees anyway?
>
>I ask because in two years of database/web programming, I've never worked
>with anyone who used any kind of naming convention other than their own
>personal style. Now I find myself defending my style in NOT using a naming
>convention.
>
>Thanks,
>Erika Foster
>
>
>---------------------------------------------------------------------------
---
>To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=listsbody=lists/cf_community
or send a message to [EMAIL PROTECTED] with
'unsubscribe' in the body.
>
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_community or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
