Yes, but any developer worth his salt should be able to pick up a *documented* methodology and work within it given an hour or so to look over the documentation. I was on a project, where the first thing they did was have me sit down with the lead developer. He dictated everything from the directory structure of the project to the casing (I.E. upper / lower case of the letters ) to use for SQL statements. I took notes, and there was never a problem. In addition to a methodology, properly documented code should be easily picked up.
At 03:05 PM 11/19/2001 -0500, you wrote: >The problem with making your own methodology up is that only the people you >have taight it to will know it, the benefit of fusebox and any other popular >methodology is that there are support forums, sample applications, and white >papers that you can work off of. > >Robert Everland III >Dixon Ticonderoga >Web Developer Extraordinaire > >-----Original Message----- >From: Zac Belado [mailto:[EMAIL PROTECTED]] >Sent: Monday, November 19, 2001 3:06 PM >To: CF-Talk >Subject: RE: Fusebox - opinions? > > > > If you are > > looking to try and instill good disciplines and readability in your code > > Fusebox is also good for that. > >This presumes that the developers know fusebox. > >You could also get this same benefit from documenting your methods and >making sure your developers follow a single standard. > >Fusebox doesn't bring anything to development (in these terms) that any >other documented methodology would. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
