Re: ILE make tools

Been in shops like that...

IMHO, the CMS isn't setup and/or being used correctly.

A CMS should make the developer's day-to-day life easier....

From experience, one big issue is that the CMS gets configured and

installed initially based on what the company and vendor believe think is
the right settings. But a) some were not right b) the environment
changes. Unfortunately, the CMS is never altered.

At the two places I've personally been involved in installing a CMS...I
reinstalled it more than once before everybody was happy.

At another much larger shop, the CMS was under the control of the "change
management team". I helped them understand what the developers needed and
worked with them to make improvements. I also got the developers to
understand that they should find the CMS beneficial...and to holler if it
wasn't! :)

Charles

On Wed, Jan 14, 2015 at 4:22 PM, Alan Campin <alan0307d@xxxxxxxxx> wrote:

Most shops I have been in developers hate them with a passion because they
can't just put stuff in that they want.

On Wed, Jan 14, 2015 at 2:19 PM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

True, but traditional IBM i CMS has deployment features valuable to even

a

small shop that VCS just doesn't have.

We paid 10K in 1996, a 3 developer license today is I believe less than
that. I'd imagine a 1-user license would be significantly less.

Assuming a developer making 60K a year. A traditional CMS that saves

even

5% of his time has a pretty short ROI.

Ironically, IT..whose job it is to make everybody else in the company

more

efficient always gets short changed on tools that can make them more
efficient. But I've found it helps to point out the irony.

I'm not saying a traditional CMS is the only solution. I just think they
are often written off way to soon.

Talk to the vendors, go through some demos haggle a bit on price since

you

are a small shop.

You might be surprised.

Charles

On Wed, Jan 14, 2015 at 3:21 PM, John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:

On Wed, Jan 14, 2015 at 2:56 PM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

But even a small shop can benefit from the control provided by a CMS;
Automated logging, source archiving in particular are helpful.

Yeah, but those pieces can be had for less. For example, you could
adjust your workflow such that modern, no-cost version control
software (like git) could be used. A traditional CMS is an
enterprise-level package, with enterprise-level pricing for
enterprise-level features. Even if the price is fair, the price is
still high, and some of those features might not provide as much value
to a single developer as they would to a group of developers.

John Y.
--
This is the RPG programming on the IBM i (AS/400 and iSeries)

(RPG400-L)

mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.