There is an end to the amount of changes a system will stand. So at one
point a rebuild is necessary. However systems will last far longer when
capable persons make the changes. Junior programmers may learn from the
maintenance experience, but I have seen to many systems maintained beyond
repair. The art of maintenance programming is vastly underrated.
On another subject: Taking risks must be worth while.
Wim
> DQ wrote in part (part of the original attribution lost -- sorry):
>
> > > Rebuild a system the customer is satisfied with? Risk his
> > > process again? Rather not.
> >
> > A special place in Hell awaits those unwilling to take risks...
>
> The real issue is whether the customer is truly satisfied with
> what has been delivered. More than once I've seen the movie where
> the customer is initially happy with what was delivered, but over
> time returns with change orders that eventually bend the original
> architecture into what could only be described as a truly tortured
> shape -- with the expected consequences for the reliability and
> maintainability of the system. Driven far enough you end up with
> few other choices _but_ to take it from the top.
>
> Chris
> Who is dealing with Just Such A Customer at the moment...
>
> --
> Chris Kennedy
> chris_at_mainecoon.com
> http://www.mainecoon.com
> PGP fingerprint: 4E99 10B6 7253 B048 6685 6CBC 55E1 20A3 108D AB97
>
Received on Tue Dec 25 2001 - 14:42:08 GMT