I was just (humbly) wondering if you could gaze your hawk eyes over the followinghttp://www.tacofleur.com/index/blog/archive/2004/01/?072043
�
It's basically a methodology I have successfully worked with for a long time
It looks more like a coding standard than a methodology ("use a coding standard" can be part of a methodology).
Specifying naming conventions and indentation is more of a religious issue than almost anything else and some of your recommendations are very controversial (specifying "tbl" as a naming prefix for tables, for example).
The most important thing when developing is code is not *which* coding standard you use but simply that you are *consistent* across all of your code - and obviously it's better if you document that consistency (as your own coding standard).
For comparison, you might like to read the Macromedia Web Team's coding guidelines (and their Mach II Development Guide):
http://livedocs.macromedia.com/wtg/public/
These can be downloaded and used as a basis for your own coding standards and modified as you wish (as long you retain an acknowledgment that it is based on the Macromedia guidelines).
Sean A Corfield -- http://www.corfield.org/blog/
"The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man."
-- George Bernard Shaw
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
