RE: "extract" command enhancement(subfiles and BIFs)

John,

Your point is valid and, no, I don't use a cheap, unprofessional attitude.  In
many shops, I may, in fact, not be _the_ expert.  I make reasonable attempts to
advance the shops I work in, in terms of documentation, standards,
templates/prototypes, etc.  However, if the client declines, as a professional,
I am bound to follow orders.  (If the client is the picture of total chaos, I
would choose to work elsewhere.)  I always try to stretch the boundaries set by
the client in ways that I think would be beneficial to them, but always try to
remain within the confines of those boundaries.  At my current client, we are
required to do _most_ of our new code in RPG III, primarily because the in-house
staff has not been trained in RPG IV.  My company has offered training classes
to the client and they refused (for the time being, anyway.)  Only when a strong
argument can be made for using RPG IV in a given situation is an exception made.

I (and another colleague) have shared and explained our RPG IV apps to a few of
the users whom expressed interest.  I would at least try to convince the client
that _modifying_ RPG IV code is relatively easy stuff for an experienced RPG III
programmer.  Seeing examples, answering "what does this do?" questions, offering
advice, etc., all in the name of advancing the shop's expertise.

The other element that affects these choices are shops that use packaged
software.  Or maybe even a home-grown system (don't see many of these anymore).
Some clients require that any new applications written in these environments use
the same style as the "package" apps, no matter how poorly coded they are.  I
guess you could call _that_ a standard if you really wanted to.

Also, I have found that the smaller shops (where I'm the only tech AS/400 person
or maybe plus a few junior programmers), believe it or not, are more open to
creating standards, using templates, etc.

All in all, John, I think we agree.  Maybe my clients have tighter wallets than
yours.  Maybe not.  <g>

>John,
>>Does your shop have iron clad type standards ...<

>As I am a consultant, "your shop" is whichever client I happen to be at.  I
>have rarely seen subfile standards, never iron clad.

>When I am allowed to create a new application from scratch (as opposed to
>modifying an existing app), assuming the shop has no standards, I use my
>own template source.  This occurrence is rare enough, though, that I still
>need to shake and bake; I guess next time I should document the heck out of
>what I do when starting from a template, eh?
>- Dan Bale


Dan

You bring up a REAL good point.  (BTW, I'm also a Consultant for more than
10 years,  For small Mom&Pop type shops to Fortune 500's with 100 people).

Standards,   Education,   Raising the Bar.   Templates,   New Code/Old Code.

If you are a consultant,   I'm sorry to say,  but you should take on the
responsiblity that that implies.   You are the Expert.   You should LEAD the
way to better
systems.   (Don't come back with exceptions please about "They hire me to do
yada, yada, yada,   Thats it"   I don't get paid for .......  If you feel
this way,
delete this,  this post is not for you)

If the shop you consult at doesn't have standards,    Suggest/Create them
!!!.     If the don't have a Field Reference,   Create one
Don't say  "Hey I don't give a rip,   It's their shop,  If they don't have
any pride,   I can sink.... I mean work at that level."

Professionalism.    If they hard code  error messages on the screen,   Lead
them to the land of Message Files and Error Message Subfiles.

On the self serving front,  You will be sowing the seeds of your own
reputation.   They will more likely re-up your contract if they think that
you
are being professional and looking out for their best interest.  Not just
putting in the hours being a grunt coder.

Build/promote a PROTOSRC type of source file.   If you have skeletons or
templates,  As you said Dan,  Document the #$% out of them,
put them in the PROTOSRC,  and let people know they are there.    YOU will
get the credit for years to come from leading the way.
It's to your best interest.

We are the ones who will have to slowly but surely inject new things into
the shops we consult for.
Show them RPGIV if they don't have it.   Ask/plead/  SELL them on the idea
that MODULAR CODE IS GOOD FOR YOU !.

If they don't have a Standards book,  start building one.  Even if it's
during stolen minutes.

The shop I consult at has one(NOW THEY DO),  and it's the first thing that
is handed out to new consultants.  Saying
Here's our naming conventions,  here's our libraries,   here' our........

Here's our PROTOSRC that EVERYONE starts with for a new program.
Heres our STANDARD SUBFILE PROGRAM.

etc etc etc.

Do you want to be the Gal/Guy  who people say,   Man,  Great stuff,   I Use
all her/his examples
they work great !!

Or the ones that they say,   OH OH,  Another Piece of @#$% from so and so ?
Your name will get around one way or another.

Ask your self this,   Would you mind if they hung up your last program on
the bulletin board
in the break room for everyone to look at or not???

Well I think you get the idea.
Lead,   Follow,  or Get out of the @#$% Way !!!!

John Carr





+---
| 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
+---