|
>After I figured out what the program was supposed to do I would rearrange it for top >down logic. By the time I was gone 2/3 of the program would be gone! Never executed code, >redundant code, endless loops. Now, someone has to come in and make a change, it's a 2 >minute job, not an all day affair. Jim What you describe is the only way to attack the problem I think. One program at a time. If anyone still subscribes to "If it ain't broke, don't fix it" Their shop deserves the RPGII/III/IV code that they had 5,10,20 years ago. I have seen this process work in 200 programmer shops and 2 programmer shops. Don't flame me on this, it's just my opinion and first hand experience. Taking one pebble out of the bowl at at time and before you know it, the bowl is empty John +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.