We brought RDP (now RDi) into our office for our developers to use, and I was excited by the fact I could continue utilizing such a tool at my new employer. One or two others within the company were also excited by this, but the majority of individuals didn't seem to share the same excitement.
The plan was to get the product in house, get the licenses, then get training. Two of those three did take place, but not the training. In the midst of getting training put together, two high profile projects came into play, and...the rest is history. Now I am not sure of the direction that RDi will take, but hope to have answers in the next month or so.
Ideally, I have touted the benefits of using RDi here, and use it every chance I get to show the benefits to other individuals. I hope through repeated exposure of this that it might catch on with others. But right now that's an uphill battle. Until then, I'll continue to use it, report any issues to IBM (along with any workarounds I come across), and hope at a future date the benefits of RDi can be realized by those who have the power to move things along here. And I'll be glad to show them what they are missing.
BTW, the product is working much better with the latest updates, which should help soothe those who choose not to use RDi based on past experiences. A few issues remain, but it's getting better.
-- Ken
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Bailey
Sent: December 19, 2013 05:16 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
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?
Important, this email transmission and any files with it are strictly confidential to the intended recipient and may be legally privileged. Any views or opinions presented are solely those of the author and do not necessarily represent those of BHSF. If you are not the intended recipient, you must not copy, disclose or distribute its contents in any way. If you have received this e-mail in error, please notify the sender and delete the e-mail from your system.
We have taken steps to ensure this email and attachments are free from any virus but do not accept any responsibility once this e-mail has been transmitted. You should scan any attachments for viruses. No contract may be concluded on behalf of BHSF Limited by e-mail.
Registered Office: BHSF Limited, Gamgee House, 2 Darnley Road, Birmingham, B16 8TE. www.bhsf.co.uk Registered in England number 35500. BHSF Limited is authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and Prudential Regulation Authority.
--
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.
This e-mail and attachment(s) may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this message is strictly prohibited. If received in error, please notify the sender immediately and delete/destroy the message and any copies thereof. Although Associated Banc-Corp and/or its affiliates (collectively "Associated") attempt to prevent the passage of viruses via e-mail and attachments thereto, Associated does not guarantee that either are virus-free, and accepts no liability for any damage sustained as a result of any such viruses. Any federal tax advice contained in this communication (including any attachments) is not intended or written to be used or referred to in the promoting, marketing, or recommending of any entity, investment plan or agreement, nor is such advice intended or written to be used, and cannot be used, by a taxpayer for the purpose of avoiding penalties under the Internal Revenue Tax Code
As an Amazon Associate we earn from qualifying purchases.