Re: Development Standards

[Keith McCully <keithmccully@xxxxxxxxx>]

I see that the shop is using a mix of RDI & PDM. Does that correlate with
age of developers or is it more to do with attitude?

Not that should affect coding standards though.

sent from Android

On 11 Dec 2016 12:25, "Joni V." <joni_vanderheijden@xxxxxxxxxxx> wrote:

> As a young one, the problem I have with cycle programs is not that I don't
> understand them or can't use them.
>
> - They lead to monolithic programs
>
> - Are harder to read
>
> - More difficult to maintain
>
> - Blocks the use of newer features
>
> - The style of a cycle program is significantly different from linear
> programs.
>
>
> So taking the arguments above into account, our more experienced / older
> technical experts agreed to disallow them in our coding standards.
>
> I have seen one new cycle program in the last four years, it was a
> one-shot program for a migration of the database where almost all records
> from a file had to be updated. I have to admit it was very performant.
>
> Joni
> ________________________________
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> on behalf of Jeff
> Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
> Sent: Sunday, December 11, 2016 12:46
> To: Midrange Systems Technical Discussion
> Subject: Re: Development Standards
>
> On Sat, Dec 10, 2016 at 10:20 AM, Raul A Jager W <raul@xxxxxxxxxx> wrote:
>
> > If we, old ones, where able to learn it, the young should be able to.  It
> > is a tool specially designed to generate reports, probably the best in
> the
> > industry, why not use it?  The fact that other languages don't have it,
> is
> > a dis advantage that we do not need to copy.
>
>
> Agree 100%.  Take the "don't use the cycle" to it's logical conclusion and
> you're saying "Don't use feature X because it's not available in every
> language out there."
>
> And no, the cycle is not the answer to every programming issue.
>
>
>
> --
>
>
> Jeff Crosby
> VP Information Systems
> UniPro FoodService/Dilgard
> P.O. Box 13369
> Ft. Wayne, IN 46868-3369
> 260-422-7531
> www.dilgardfoods.com<http://www.dilgardfoods.com>
>
> The opinions expressed are my own and not necessarily the opinion of my
> company.  Unless I say so.
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD