I think that if you really want code standard adoption, it has to be built into the tools you are using (ie. eclipse) and also your build environments (ie. hudson) or some other way to automate and report on adherence.
I'd also think it would work best on a greenfield project as forcing code standards on legacy code (or even more recent code) could be quite time consuming and (if automated) my loose some of the original developer's layout that provided semantic meaning. On Aug 3, 3:22 pm, Brett Payne-Rhodes <bret...@gmail.com> wrote: > I've been looking at published CF coding standards and guidelines and just > thought I would share this gem... > > Which do you think came first? > > http://cf.etisbew.com/home.cfm?file=codingstandards.htm > > or > > http://www.brevardcounty.us/is/webdevguide/codingstandards/cfml/cfmlg... > > Blatant plagarism like this makes me wonder what else they might be > borrowing... > > If you have a public coding standard that you would like to share I'd been > to hear about it. So far Sean Corfield's old CFMX coding standard > athttp://livedocs.adobe.com/wtg/public/coding_standards/contents.htmllooks > like the best place to start... > > B) -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaus...@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
