thank you all for the feedback. this is my first time i am in a position where i have oversight over the development in a team, so i'm thankful for the insight from you who have this experience.
the bulk of a proposed coding standards dealt with topics such as making moves toward more "web standards" compliant markup code, not using IE only DOM references, proper scoping of variables, especially in CFCs, some basic guidelines for more efficient SQL, etc. the issue i was running into was that there wasn't any consistency, even from the code developed by individual developers. often, i came across things like long sql statements in cfquerys and stored procs on one line, or the random use of capitalization of variable names in a single file. i've always been of the mind that these "stylistic" details should follow the general rule of being consistent and readable, but have found that just broadly stating it isn't necessarily clear to everyone what that is and prompts the question of what that specifically means. i debated back and forth with myself as to whether to put these in a coding standards doc, or to address these on an individual basis. i decided that the most pragmatic route was to put them in the doc, so that even if they were not "complied" with, they could be used as an example of code that was consistent and readable. i've seen some of these discussions before in the cf community, and i'm of the opinion that these stylistic choices shouldn't be in a community best practices or standards doc, but was wondering if others have found them helpful in the context of a team with members of varying skill sets. On 10/7/07, Dave Watts <[EMAIL PROTECTED]> wrote: > > > " Consistency is important, the minutiae of capitalization > > and whitespace is not." > > > > I don't agree with this, as standards go the whitespace (tab > > obsession) is very important. > > > > Take this example (might not come out right on email. > > > > Select * > > From Table > > Where X = 1 > > And Y = 1 > > > > And this > > > > Select * > > From Table > > Where X = 1 and Y = 1 > > > > These are different standards, if you get used to reading the > > first, you easily miss the second part of the where in the second. > > Perhaps, but neither is superior to the other. Pick one and go with it - > that's Sean's point. That's consistency. > > Dave Watts, CTO, Fig Leaf Software > http://www.figleaf.com/ > > Fig Leaf Software provides the highest caliber vendor-authorized > instruction at our training centers in Washington DC, Atlanta, > Chicago, Baltimore, Northern Virginia, or on-site at your location. > Visit http://training.figleaf.com/ for more information! > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion 8 - Build next generation apps today, with easy PDF and Ajax features - download now http://download.macromedia.com/pub/labs/coldfusion/cf8_beta_whatsnew_052907.pdf Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:290515 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
