Re: It might be time for a refactor when...

I fully support indentation, spacing, and meaningful object names as
documentation tools--it's the "style" discussion.

If I see four rows of asterisks, a comment like "This program updates the
customer master", and another four rows of asterisks, I'm going to look at
the rest of the code and work with the coder to ensure s/he's thoughtful
with every line of source code entered, regardless of whether it's compiled
or not. Documentation should not be fluff.

It's a necessary step on the path from coder to programmer to developer.

On Tue, Jul 23, 2024 at 3:23 PM VERNON HAMBERG Owner via RPG400-L <
rpg400-l@xxxxxxxxxxxxxxxxxx> wrote:

Raul took us down a path that, so far as I understood, was not the
original intent nor the original question - for me, refactoring is in the
code, not the interface. The original issue was that he had hit a limit of
the number of lines of code, and that was a call for refactoring. I
suggested to at least 1 person that service programs could take a lot of
lines of code from a monolithic source member. That could lead to other
differences, of course.


And I agree with Jim, not everything works well in the WWW.

Cheers
Vern


On Tue, 23 Jul, 2024 at 4:39 PM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:


To: rpg programming on ibm i

Not all applications lend themselves to a web based interface. One IBM
i based company implemented SAP at the counters at all locations.
Transaction time went from several seconds to almost 2 minutes.
Contractors waiting for their parts for the day lost time waiting and
eventually found other suppliers. Sales went down, they had to build a
faster interface to fix it. Cost lots of lost sales and time to fix it.
They recovered but at what cost? The web based apps are not always the
solution.


Jim Oberholtzer
Agile Technology Architects

On Jul 23, 2024, at 3:46 PM, Raul Alberto Jager Weiler <

raul.jager@xxxxxxxxx<mailto:raul.jager@xxxxxxxxx>> wrote:

You era right, it is necessary to plan for clean up.
And it takes practice to get used to the stateless environments, but once
you get used to it you will never miss the state full conexión.
The clean up is a small price compared with the advantages of the

stateless

conexión.

El mar, 23 de jul de 2024, 15:11, Daniel Gross <daniel@xxxxxxxx<mailto:

daniel@xxxxxxxx>> escribió:

Von meinem iPad gesendet

Am 23.07.2024<http://23.07.2024> um 18:58 schrieb Raul Alberto Jager

Weiler <

raul.jager@xxxxxxxxx<mailto:raul.jager@xxxxxxxxx>>:

Also, the use of green screen or fat clients is a good reason to

refactor.

WEB user interfaces is much better.

Of course, web interfaces are the current "state-of-the-art" - but I

have

to say, that (at least IMHO) they lack one important feature: Stateful
Transaction Processing

All web interfaces are stateless by definition. They emulate a
statefulness by utilizing a bunch of technologies, like a shopping cart

or

a session token or something like that.

But in the end, if an session ends "abnormal" - there have to be

timeouts

and algorithms that detect inactive sessions to rollback database

actions -

where an aborted green screen session does all that without any

application

overhead.

So when in comes to transactions - maybe a stateful and transactional

user

interface is not the wrong choice.

Just my 2ct
Daniel
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx<mailto:

RPG400-L@xxxxxxxxxxxxxxxxxx>

To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx<mailto:

RPG400-L-request@xxxxxxxxxxxxxxxxxx>

Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:

support@xxxxxxxxxxxxxxxxxxxx> for any subscription related

questions.

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx<mailto:

RPG400-L@xxxxxxxxxxxxxxxxxx>

To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx<mailto:

RPG400-L-request@xxxxxxxxxxxxxxxxxx>

Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:

support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx<mailto:
RPG400-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx<mailto:
RPG400-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:
support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.