× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I've tried to stay out of this type of topic, because the spam makes me
eventually end list transmission to my email box for a while. But I can no
longer resist: I use RDi. Some of my coworkers prefer SEU. Is it really
necessary that everyone conform?




From: "Grace, Casey" <CGrace2@xxxxxxxxxxxxx>
To: "wdsci-l@xxxxxxxxxxxx" <wdsci-l@xxxxxxxxxxxx>
Date: 12/19/2013 11:24 AM
Subject: Re: [WDSCI-L] Promoting WDSCi, RDp and/or RDi
Sent by: wdsci-l-bounces@xxxxxxxxxxxx



Paul,

I too feel your pain. I haven't had much success with getting the
retrogressive green screen programmers to move to RDI either. I even had
one say it was too hard on the eyes. Really? So, I changed the background
to black and the text to green and said - Hey! Check it out! It even looks
like green screen! Ya gotta love it! He didn't find it as funny as I did.
I agree with whattsson's response , "green screen" programmers just DO NOT
want to learn new things, they will use any excuse not to. This, I've seen.

These days, on the rare occasion that I'm forced to use SEU, I can't stand
it. It hurts my brain to go back in time.

Casey


message: 5
date: Thu, 19 Dec 2013 11:16:19 +0000
from: Paul Bailey <PaulBailey@xxxxxxxxxx>
subject: [WDSCI-L] Promoting WDSCi, RDp and/or RDi


I've been using WDSCi/RDi/RDp (from now on, just RDi) for many years, and I
have been the primary (if not sole) driver in getting my colleagues to use
it.

In discussions with my colleagues I point out the features that make things
easier, the tools that could make their programming lives just a little
better. This is a tough argument because SEU/PDM still does things that
can't be done in RDi, but I usually have a 50% success rate in the number
of colleagues adopting RDi. The facts that SEU is now static even if RPG is
not, and the general usage of an Eclipse tool will help advance/expand
their careers and skillsets are also strong arguments. The learning curve
is a downside, but I try to skirt around that.

I'm under time constraints all the time. It takes an hour or more to
install and/or upgrade RDi and that time is often precious and needed
elsewhere, so at the moment I am the only user in my company using the
latest version (9.0.1). Two of my colleagues are still using v8.5 and today
*both* of them came across the bug where source was saved in RDi but didn't
turn up on the IBM i (no errors, the source just didn't get transferred.)
There were tantrums, rants and toys were thrown out of prams (slight
exaggeration, but you get the idea?) and now both are refusing to use the
tool until it is updated. Their faith in the tool, and in my advice, has
been damaged.

I guess I am just venting my frustration here and I apologise for bending
your ears (screens?) but I am just wondering how successful others are at
getting their colleagues to use the tool. What are your best arguments for
all the SEU-fanboi nay-saying, and how do you recover from faith-damaging
errors such as the one my colleagues suffered today?


-Paul.


PS Can I get some commission from IBM for being the only person in four
different companies over the past 10-15 years that has championed RDi?






--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.



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.