Re: MIDRANGE-L Digest, Vol 16, Issue 415

Now i know i'm not alone. <g>

I'd like to go to them and say "here's what we should be doing, and

here's

why we should do it".

If you can explain technical debt to your management in a way that
shakes out money and time for repairing it, please share your technique!

Yep there's the trick!

I do what i can, bit by bit, but something (it seems to me) this

important

should gain purchase as a bonafide project/goal.

Despite my sourness above, there is hope. That hope is gradual
refactoring. Which is a hard problem! But the point is that I have
been able to make new tables/views/functions/procedures on the way to
implementing new functionality. Sometimes I need a trigger to
temporarily (ha!) populate the 'new' side, but I can write triggers in
RPG, and so put conversion logic in where needed.
I'm doing that, right now, without any mandate from on high.
--buck

Yes, currently my 'unmandated' method of choice.. gradual refactoring.

xxxxxxxxxxxx
<br />
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else is
unauthorized. If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on it, is
prohibited and may be unlawful.