RE: RPG naming

By no means am I an expert on refactoring. My take is it's a methodology
for improving code reliability, readability, maintainability, and, when
applicable, reusability. In many cases the result will be the creation
of sub-procedures and/or service programs. In other cases it might just
be breaking large code blocks into smaller, easier to read sub-routines.

There's no 'agenda' per se, (at least there shouldn't be) except to
improve the code.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, October 11, 2005 10:37 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: RPG naming

Would that be like busting down a huge monolithic program into several
modules, but the what comes in and what goes out remains the same?

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Cate, Tony (Alliance)" <JACate@xxxxxxxxxxxxxxx> 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
10/11/2005 09:17 AM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
"RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
cc

Fax to

Subject
RE: RPG naming






Refactoring is not debugging. Here's a brief descriptin of what it
is/does:

Refactoring is a disciplined technique for restructuring an existing
body of code, altering its internal structure without changing its
external behavior. Its heart is a series of small behavior preserving
transformations. Each transformation (called a 'refactoring') does
little, but a sequence of transformations can produce a significant
restructuring. Since each refactoring is small, it's less likely to go
wrong. The system is also kept fully working after each small
refactoring, reducing the chances that a system can get seriously broken
during the restructuring.
 

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Tuesday, October 11, 2005 9:10 AM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: RPG naming

I disagree, and here's why: for whatever reason, new IT professionals
today seem to find it necessary to rename everything before they'll use
it.  My favorite is using "refactoring" instead of debugging.  But the
trend continues: they need a name for everything.  One of the latest has
been "constructor dependency injection".  What is this?  It's parameters
on the constructor!  WHOO HOO!

To be fair, the true constructor dependency injection concept is more
complex, involving metadata and a number of relatively advanced
techniques, but many people who use the term use it simply as a way to
put a name on adding parameters to the constructor.

What causes this?  It might be a way for newer programmers to shield
themselves from the fact that everything was actually written back in
the 60's and we're all just re-implementing it.  Those of us who started
in the 70's and inherited directly from that generation seem to have
less problem with this concept, but each succeeding generation seems to
want more "credit".  Maybe it's just that when I started all this stuff
was pretty hip and new, wheras today to admit you're using 40-year-old
concepts might seem highly uncool to newer programmers.  Of course,
mathematicians (of which we are a highly specialized subspecies) proudly
use theorems that are hundreds or even thousands of years old, so maybe
it's just a lack of classical training <grin>.

In any case, renaming RPG might just cause new programmers to see it as
a new beast.  And frankly, the RPG /free syntax is different enough,
with its BIFs and procedures, to warrant a name change.  But that's just
me.

Joe


> From: rick baird
> 
> it won't matter to existing non-iseries IT professionals/language 
> bigots.  they will see it as nothing more than putting lipstick on a 
> pig, and will pay little attention.  It will have about as much an 
> impact as as/400 -> iseries -> i5.

--
This is the RPG programming on the AS400 / 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.