Re: Need some ammunition (Procedures vs. Sub-routines)

Wow - sounds like you are running into some old problems there. 

First, find out why the initial decision was really made, and then if at all possible, explain and praise the decision. 

Then explain how what you want to do fits in with that policy, and how, because of advances in the OS and Language since whenever, it should not cause any more of a testing issues than a typical subroutine. 

Go on to explain that this makes the code more reusable, and by doing so can save time and money. 

Then suggest a trial or test of the idea, so that the results can be evaluated. It would probably be a good idea to have on hand exactly what you would suggest to use a trial, and explain why. 

Usually companies make rules like that for good reasons, I mean besides trying to stay in control of a runaway technology like computers and software. Try to find and support those reasons. :) 

-Paul


On Dec 27, 2013, at 10:51 AM, RPGLIST <rpglist@xxxxxxxxxxx> wrote:

I won't go into the entire lengthy and boring conversation I just had with
upper management, but I was basically told that under no circumstances am
I to add procedures to certain applications. The justification is that
by doing so, we will be required to re-test the entire system, payroll,
dispatch, load balancing, AP, AR, etc.

I however was provided an opportunity to make my case, and I have a list
of reasons, but I need every bit of ammunition I can come up, so any help
from ya'll would be cool.

Dutch