I wish I could find a way to not be your enemy - it would make
collaboration so much easier and fruitful. I do realize in the past I've
been an asshole on these forums. I ask for forgiveness, publicly, for any
ways I have wronged you.

With that said, your question is relevant and should be considered not just
by CIO/CTO roles but also Presidents and CEOs. Or rather, because
technology is what drives business success it also needs to be a business
decision that extends beyond the IT dept.

The longer I am in business the more I get involved with higher level
decision makers and can gain their perspective. They do care about
retaining investment (i.e. RPG) but they also care about beating
competition, and that means time to market. There's a very healthy medium
with open source stacks where you can retain your investment in RPG
(XMLSERVICE and language specific wrappers, iToolKit in Node.js's case) and
still get to market in timely fashion by capitalizing on many thousands of
open source contributions.

And that is the question you are asking... who will take over after Aaron
retires or gets hit by a bus? Who will take care of code Aaron developed
for his customers? Who will take care of products Aaron created for
KrengelTech?

To that I can say there are literally millions of (Ruby, Node.js, Git,
Java, PHP, Python, GCC, etc) developers world-wide. That was a strategic
business decision both for in-house and customer development. We serve
both sides best when we adequately measure business risk/liability and act
accordingly.

Aaron Bartell
litmis.com - Services for open source on IBM i


On Mon, Oct 19, 2015 at 7:48 AM, Henrik Rützou <hr@xxxxxxxxxxxx> wrote:

Aaron

let me ask you a simple question ...

"Who is going to maintain the trail of different programming technologies
you
leaves behind you when you choses to leave the building?"


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.