|
On Tue, Aug 18, 2015 at 1:06 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:
On 8/18/2015 12:00 PM, Dan wrote:the
My
supervisor did not give details on what the issues were, as they rarely
need to touch the affected applications anymore, so I don't know what
exact issues were. But, obviously, the battle scars are still kinda raw.
Before Buck gets into potential technical issues, I would like to take
a side trip to another thing he wrote. It was regarding a thread on
this list titled
Need some ammunition (Procedures vs. Sub-routines)
The particular post is
http://archive.midrange.com/rpg400-l/201312/msg00348.html
It has to do with recognizing when the challenges are emotional rather
than rational (which is probably most of the time; and in my
experience, it never hurts to assume there's at least a significant
emotional component).
leadersI may be asked to present my case to the "group of 3" development
well,here, and it would be nice if I can present how to overcome the typical
challenges. If anyone is aware of articles that discuss this and, as
the benefits to using service programs, I would appreciate links.
Can't say I know of a 'fan page' for service programs but [...]
I guess this list in part serves the role of fan page. But it's not
like there's one link. It's more of a recurring topic of discussion.
Two threads that I think are worth reading are the one I mentioned
above, which started in Dec 2013 and continued into Jan 2014. Another
is from Jan 2015, titled
Service programs, procedures, not sure what to do
(I give the subject lines and the months because it may work better to
just go to the relevant monthly pages in the archives rather than
using the search feature.)
This list has pretty much reached consensus on best practices for
newcomers to follow.
Has it? I know you have a pretty good idea what to recommend
newcomers, based on your own experience, but my impression is that
there are always disagreements on the approach to take. Mainly,
there's a camp which seems to advocate trying to push "expert
practices" as early as possible, so that newcomers have the most
direct path possible toward expertise, and have the least chance to
settle into "initially easier but ultimately suboptimal" habits.
The other camp (which I perceive you to be in, but I'm speaking as
someone with almost no service program experience myself) emphasizes
making things as easy and undaunting as possible, so that there's at
least *some* movement. Of course, there's an attempt not to promote
actively bad practices, but "good enough" is good enough, especially
if it's already significantly better than the status quo.
Not all the disagreements fall neatly into that dichotomy either. For
example, when you describe binding directories, you make it sound very
newbie-friendly. But when Alan or others talk about Make tools (and
the futility and frustration of binding directories), that certainly
sounds newbie-friendly as well.
In any event, I just wanted to share a couple more links, again to
Buck's "mini-tutorials" (you seem to write one at the beginning of
each year). These are both from the threads I mentioned above:
http://archive.midrange.com/rpg400-l/201401/msg00076.html
http://archive.midrange.com/rpg400-l/201501/msg00025.html
The one from Jan 2014 in particular seems almost ready-made for a wiki
on the subject.
John Y.
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.