Use source control. Do not hard code. Use a config file. Use a logger. K.I.S.S. google.com Right tool for the job. As far as docs, use good comments and a simple README; if someone needs a Word document with tables, graphs, and charts they'll ruin your code.
*All this can be changed depending on the circumstances. On Wed, 24 Jul 2002, G wrote: > Does anyone have a project management book or class they recommend? I'm > in a non-fusebox environment with no project manager. It's pretty much > "cowboy-coding". We're handed a "Marketing Spec Document" and turned > loose. I've used FB for a few years, and am kind of lost without it. I > know I'm starting to write code way too early in the scheme of things > before prototyping or even creating a "Technical Spec". I'd like to > incorporate wireframes/fusedocs or the like into a system. Anyone have a > system or ides they'd like to share? > > Thanks. > ______________________________________________________________________ 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
