John,

I agree that matching the style of an existing program so that the style is more-or-less consistent throughout that particular source member is nice.

But I don't agree that in the larger sense you should always use a style your staff is comfortable with.  Comfort is good to a point -- but if you never step out of your comfort zone, it can hold you back.

For example: Sticking with a fixed-format programming style today is bad for your business.  All new features added to the environment are added in free format.  New developers who learn RPG in school do not learn fixed format.   Making a rule that your staff cannot advance because not everyone is comfortable with it is a poor choice.

Rather, people should be encouraged (or, in some cases, "forced") to continue to grow and improve and learn new techniques.  You cannot let yourselves get stuck in the past, unable to keep up with changes in the IT industry because your developers aren't willing to update their style.

-SK

On 3/10/2020 11:04 AM, Voris, John wrote:
Jon Paris wrote:
Why? In fact if you;'re going to just do the same old same old why bother to change to free?
Surely the whole point of changing is to get to use better methods.
I will disagree with Jon here.

The whole point of Programming is to make the code legible and easy to read - easy to follow - and easy to comprehend.
If flipping from one standard to another within a block of code is not something that your staff is comfortable with, then you should not do it.

"Choice of Style" is just another micro-decision that we make as we insert new logic into existing programs and existing blocks of code.

John Voris
Philadelphia

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.