My point was, I suppose, that very few people really seemed to LIKE
code/designer, but it was the ONLY client-based alternative to SDA.
When this is all you got, you'd better find something to like about it,
otherwise just simply do without. Code/Designer was ok as an
alternative to SDA. I'm glad it's now gone.
I *believe* that I am more productive in the IDE, and I appreciate you
trying to get the word out. But what I seem to be seeing is management
asking for us to prove ROI, and nobody seems to know how to quantify it.
Maybe we need an article about how to prove what and where the
productivity gains can be measured.
What does one measure? How does one determine quality of code? IMO,
the IDE could contribute to higher-quality code by encouraging use of
descriptive field names. Outline and code completion take the sting out
of using qualified DS. /Free syntax helps define structure and flow of
the code... The IDE in theory *could* be beneficial on all these
counts, but impossible to quantify, I think.
Sorry if I'm being dense here, but I'm frustrated that I cannot find any
compelling way to *prove* to anyone that I am more productive with the
IDE.
-Eric
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Joe Pluta
Sent: Thursday, March 25, 2010 3:45 PM
To: Rational Developer for IBM i / Websphere Development Studio Client
forSystem i & iSeries
Subject: Re: [WDSCI-L] RDp v7.5
DeLong, Eric wrote:
Joe,
Who said they "liked CODE so much"? I used it (CODE/Designer) simply
because it was the only client based alternative to SDA. When I use a
tool, I naturally try to find ways to use it effectively, and over
time
come to appreciate some of its good points. Is it really so different
for you? Really, I think EVERYBODY is happy that IBM finally
delivered
this piece, so why are we stuck in the mud here?
Eric, I'm sorry, I'm not even getting the gist of this message. My only
point that I don't know diddly about CODE. From what I remember, it had
a decent enough interface but still sort of VB-ish, and it occasionally
blew up. All I was saying to Vern was that since he seems to like it,
and if indeed Screen Designer is the same thing then he'll have an easy
transition.
IMO, despite the usefulness of Screen Designer plugin, that developers
will still fail to use the new tools. Too much focus on lowering
cost,
and an inability to quantify efficiency/quality/productivity/cost
gains
make this a non-start for many shops...
Well, one big pushback was that you had to either buy ADTS or RDi and it
was hard to give up ADTS because of SDA. With RDPi, that particular
hurdle is gone.
Will developers use the GUI? I dunno. I hope they do; they *will* be
more productive. And so I keep evangelizing.
Joe
midrange.com
