tag:blogger.com,1999:blog-7771849611629554528.post6771583556275150417..comments2009-11-15T12:55:23.513-08:00codoholichttp://www.blogger.com/profile/07724024058205041400noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7771849611629554528.post-71903041483003778762007-01-17T14:09:00.000-08:002007-01-17T14:09:00.000-08:00There is no doubting that requirements specifications are necessary. Good functional documentation is necessary. <br /><br />What I am questioning is the elaborate documentation of the source code so that some one coming in to the team can understand it. That may have made sense in days of procedural programming but these days of J2ee , .net programming with all sorts of framework its simply may not work.<br />I have browsed through lots of open source software. They have user documentation, also documentation on what problems a given OS software solves. But absolutely nothing to very little code documentation. If you want to participate browse through the code , that seems to be the messagecodoholichttp://www.blogger.com/profile/07724024058205041400noreply@blogger.comtag:blogger.com,1999:blog-7771849611629554528.post-13079313894991467462007-01-17T11:12:00.000-08:002007-01-17T11:12:00.000-08:00<i>...asked me to document my Applications.</i><br />What audience were the documents written for?<br /><br /><i>... they will prefer the source code ...</i><br />Will the source code tell them why the code was written?Isaac Gouyhttp://www.blogger.com/profile/05398229396333413000noreply@blogger.com