Agreed on the simple, top-down code with adequate documentation built in. FROM this kind of code, specs can be reverse-engineered. Then those specs can be presented to those utilizing the product to make sure THOSE specs fit the task at hand.
And some advise I took from 'The Mob': "I don't trust anything I didn't write and only half of what I did." David Laansma IT Manager Hubbard Supply Co. Direct: 810-342-7143 Office: 810-234-8681 Fax: 810-234-6142 www.hubbardsupply.com "Delivering Products, Services and Innovative Solutions" -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of David A Barrett Sent: Wednesday, October 14, 2009 3:42 PM To: [email protected] Subject: Re: [U2] U2-Users Digest, Vol 6, Issue 12 My experience is exactly the opposite. Well written, simple code that approaches its function in straight-forward manner is worth 1000 lbs of specs and documentation. I never, ever approach a maintenance project under the assumption that the documentation from back when has any relevance to the current functioning of the programs in question. On the other hand, the running code is guaranteed to be a totally up to date record of how the system is currently working. Dave Barrett Project Manager, Lawyers' Professional Indemnity Company (LAWPRO®) ----- Original Message ----- Date: Wed, 14 Oct 2009 11:59:58 -0400 From: "Susan Lynch" <[email protected]> To: "U2 Users List" <[email protected]> Subject: Re: [U2] Unibasic: Sample program - to extract data from Table Message-ID: <009401ca4ce7$61abdd10$65fea...@susanhome> Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original As a programmer who has had to maintain and enhance systems that were written apparently based on a one-page spec that "everyone on the team" understood, when the team members are no longer there, and the documentation was all between their ears (and left with them), I am a big believer in detailed written specs that get turned into test plans and then into documentation. Eventually the lack of specs turns around and bites the organization that allowed it to happen (unless the application was a one-time quick-and-dirty project that will never have to be resurrected). Susan Lynch This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please delete it and advise me (by return e-mail or otherwise) immediately. Ce courrier électronique est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courrier électronique par erreur, veuillez le supprimer et m'en aviser immédiatement, par retour de courrier électronique ou par un autre moyen. _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
