begin quoting Paul G. Allen as of Sun, Mar 16, 2008 at 11:06:44PM -0700: > SJS wrote: > > > >I also wouldn't worry about writing the documentation for more than > >one a method or class. Writing out the documentation for the whole > >project before you write any code? I agree -- not useful. > > I've found it very useful. I've found that by the time I've documented > everything in a proper SDD, I know exactly what I'm going to write when > I start coding. At that point, the coding is easy since I already know > what it's supposed to do.
When I've been on teams that did that, the result was a truly terrible design. Of course, heavy use of UML may have contributed to that as well. > Sure, some portions of the documentation will need to changed or added > as the coding moves forward, but the entire SDD and API won't have to be > modified or created from scratch. Sounds like you're solving problems that you already know how to solve. -- Not all programming tasks are the same, it's hard to call, sometimes. Stewart Stremler -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
