Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Joel on Software
Message
 
To
18/05/2005 11:23:20
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
01014573
Message ID:
01015581
Views:
31
>>Don't you ever work with other people's code or go back to your own code much, much later? That's when naming conventions shine. When I can pick up a piece of code I wrote 5 years ago and immediately know the data type of the variables involved, I save a lot of time and energy and am much less likely to make mistakes in modifying that code.

Hi Tamar,

I can't believe there's even a debate on this issue. Naming conventions are a MUST as far as I'm concerned. I can easily read my code and the code of others and know what's going on. We also adhere to a strict naming convention for our tables -- each table uses a unique 3-character prefix for all fields in the table. This naming convention makes it EXTREMELY easy to know exactly where a piece of information came from .. and to know exactly what the name of a field is without having to look it up. It really helps with bringing new developers up to speed very quickly.

Cathy
Cathy Pountney, Microsoft Visual FoxPro MVP
Memorial Business Systems, Inc. (www.mbs-intl.com)

My Website: (www.frontier2000.com)
My Blog: (www.cathypountney.blogspot.com)
My Book: The Visual FoxPro Report Writer - Pushing it to the Limit and Beyond
Free MSDN Article: What's New in the VFP 9.0 Report Writer
Free MSDN Article: The VFP 9.0 Report Writer In Action
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform