RE: ILE vs. non-ILE

[Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>]

-snip-

>However, there are also folks
>on the team who oppose, or are apprehensive,
>implementing ILE.  We go back and forth debating
>the related issues and have had some great conversations.
>
>Our development shop is large and some of the concerns
>expressed are centered around the learning curve associated
>with the whens, whys, and hows of ILE.

Having had to endure these arguments, I have one very unpleasant thing to
say.  If your technical staff have apprehensions about using modern coding
practices or have concerns with learning new techniques, then your
organisation is poorly positioned to be in the software business.  Aren't
programmers who press for the new shiny toys more desirable than those who
shy away from learning something new?  (I know YOUR answer, Kevin! <grin>)

Our previous management (we've since been sold again) and technical staff
were precisely in this position and I would completely agree that we were
poor developers writing poor code.  "Bearskins and stone knives" is the
expression that most readily comes to mind.

-snip-

>I am looking for case studies, horror/success stories, and any
>other nuggets related to implementing ILE.  If there is anyone
>out there who's gone through a similar exercise, I'd love to
>hear about it.

About the only key concept that's Really Important is that you will want a
librarian to track the creation of new functions.  If Jane writes a "number
to words" function for the A/P check system, and Dave writes another one for
the P/R system and Josie writes another one for the G/L system...  Well you
get the idea.  There needs to be a way that the team members can find out if
a function has already been written.

The technical aspects of ILE aren't that many or complex.  How to name your
AGs (don't - have "menu level" programs be *NEW and all the rest *CALLER.)
How to include prototypes (/COPY from QPROTOSRC)  Maybe more; none spring to
mind at the moment, but perhaps this part of my post will spark a meaningful
debate.

-snip-

Good luck!
  buck