From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Thread: 103376,3869f0598191b11d
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news1.google.com!news.glorb.com!border1.nntp.dca.giganews.com!nntp.giganews.com!ngpeer.news.aol.com!audrey-m2.news.aol.com!not-for-mail
X-Admin: news@aol.com
From: softcrafts@aol.com (Ronald Price)
Newsgroups: comp.lang.ada
Date: 17 Aug 2004 04:28:23 GMT
References: <g8-dnUjV8tx6PGDdRVn-rA@megapath.net>
Organization: AOL http://www.aol.com
Subject: Re: Porting ADA source
Message-ID: <20040817002823.04158.00003023@mb-m15.aol.com>
Xref: g2news1.google.com comp.lang.ada:2763
Date: 2004-08-17T04:28:23+00:00
List-Id: <comp.lang.ada>

Good observation Randy.

I have had to design, re-engineer, and refactor code because it was not created
for maintenance.   

I have been told that the Quick and Dirty approach is the best, I was taking
too long, etc.  But I knew if I organized the code for repair in only one place
my job later as the maintainer would be significantly easier.


How do we teach these maintenace concepts except by OJT?