Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.42!gegeweb.eu!nntpfeed.proxad.net!proxad.net!feeder1-2.proxad.net!usenet-fr.net!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!feeds.phibee-telecom.net!usenet.ukfsn.org!not-for-mail From: Martin Gregorie Newsgroups: comp.lang.java.programmer Subject: Re: Standard Design and Development Methodologies Date: Sun, 27 Nov 2011 20:07:19 +0000 (UTC) Organization: UK Free Software Network Lines: 25 Message-ID: References: <9j25r6FpfU1@mid.individual.net> <4ed05727$0$289$14726298@news.sunsite.dk> NNTP-Posting-Host: 84.45.235.129 Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: localhost.localdomain 1322424439 738 84.45.235.129 (27 Nov 2011 20:07:19 GMT) X-Complaints-To: usenet@localhost.localdomain NNTP-Posting-Date: Sun, 27 Nov 2011 20:07:19 +0000 (UTC) User-Agent: Pan/0.135 (Tomorrow I'll Wake Up and Scald Myself with Tea; GIT 30dc37b master) Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:10280 On Sun, 27 Nov 2011 08:39:55 -0800, Patricia Shanahan wrote: > On 11/27/2011 4:34 AM, Arved Sandstrom wrote: > ... >> The only thing that stays with the code - reliably - *is* the code, >> including comments. > > This is one of the reasons I love Javadoc, and similar systems. A > comment block right next to the thing it describes stays with the code, > and is more likely to get updated during maintenance than any other form > of documentation. > I agree completely. At the other end of that scale, back in the early '80s I was contracting in a large mainframe shop. Their systems analysis and design group had a policy of actively destroying documentation as soon as their involvement was finished, regardless of how big or small their input to the project or change request had been. -- martin@ | Martin Gregorie gregorie. | Essex, UK org |