It's always hard to fill the shoes of someone who has gone before, and Bob Cozzi's decision to step away from this newsletter has left MC Press Online with a challenge: How do you replace a teacher who has proven to be as intelligent, thoughtful, and experienced as Bob Cozzi?
The answer is "You don't!" Instead, you take a look at what the readers need to know, and you aim to find the best talents available to promote the mission.
What is the mission? RPG, of course! And everything it touches!
Modern Languages and Modern RPG
A person high up in the echelons of the corporate IBM world (who shall remain nameless) sent me an email that smacked a bit of typical big-IBM chauvinism. He asked me rhetorically, "How can we move the cult of RPG programmers into the modern world?"
By this, he evidently meant moving RPGers to the so-called "modern languages" that his corporation has spent years promoting. What these individual languages are and have been, of course, has evolved over the years: First there was PL1, then C, then C++, then SmallTalk, and currently, Java—in support of IBM's WebSphere middleware platform.
Now, don't get me wrong: We're not in a programming language war. Each of these languages has its merits, and each has had strong, knowledgeable proponents. In fact, I've heard some of these proponents tell me, every five years, that RPG is dead, only to have them come back to me later to inform me that though they'd now moved onto yet another programming language, in their view, RPG was still dead!
Dead? This so-called "modern world view" of programming languages seems strangely divorced from the real world of System i programmers! What is considered "modern" seems to be merely "hot." And the proof is that RPG is still here and still thriving, while many of those IBM-sponsored languages are but distant memories. Why? Because RPG is what academics call a post-modern language: a classic with a lifeline that debunks the myth of obsolescence.
Legacy Versus Cadillac!
To my way of thinking, RPG is clearly not a legacy. It's a Cadillac! Not only is it a vibrant and highly productive tool used by literally thousands of developers day in and day out to maintain legacy code, but it's also a luxury vehicle used to build new and productive applications that are vital to the business community. And it is being used because, when the dust settles, it is the heart of the System i developer community and all that this community has come to expect in a luxury language!
Getting the Message Out
Of course, getting this message up the IBM food chain is not our goal here at RPG Developer. Instead, our message is to let you know not only that RPG Developer is alive and well—and still dedicated to the RPG language—but that we intend to transform this newsletter into something that you and your organization can better use.
In the coming months, we'll be transforming RPG Developer to do more than merely fill in the blanks of your personal RPG knowledge. We'll evolve this publication to help expand the use of the RPG language within your organization.
Best Team of Educators
First, we have nearly finished lining up one of the hottest RPG editorial teams of educators on the planet. These are professionals who not only know and use RPG on a daily basis, but have built their careers around expanding the use of the language in business environments just like yours.
Second, we've engaged one of the best educators in the industry to prepare step-by-step tutorials that your organization can use again and again to train and educate the next generation of RPGers—first, in the use of the tools used to construct RPG source, and later in the implementation of the key functions that make RPG so powerful to the business community.
Beyond the RPG Blog!
In the past, the value of RPG Developer was that it was almost a personal blog written by one of the industry's most renowned RPG authors, Bob Cozzi. Our goal is to move beyond the personal blog to enhance your involvement in the RPG community at large.
So if you have questions or queries or ideas about RPG–related areas that need to be explored, we welcome your input. We'll try to build our editorial schedules with those ideas in mind. And if we don't know the answer to a particular question, we'll do our best to find it for you.
Our mission statement is the same as it has always been: RPG all the time! But we're doing a bit of remodeling as we move forward with the new RPG Developer: Now it's RPG and all it touches all the time!
Drop us a note with your suggestions! I think you'll find the new RPG Developer will meet and exceed the expectations of all you've come to love about this newsletter.