Leveraging AI and Automation in RPG Development
Coffee, Code, and the Future of IBM i
My Daily Coffee and Final Sips: The Cariboo Lakeshore Blend Ritual That Sets the Tone
Before diving into the complexities of RPG code and AI tools, I start
each day with a ritual: brewing a fresh pot of Cariboo Lakeshore Blend.
The smooth, rich aroma helps me shift from personal mode to problem-solving
mode. It's more than caffeine—it's intention. I review my top priorities, scan
my Panda Planner, and set one clear goal for the day.
Later, before signing off, I take a moment for my “final sips”—a
brief pause with that same blend. It’s a quiet checkpoint: What did I solve
today? What did I learn? What should I tee up for tomorrow?
RPG Development Meets Modern Automation
RPG has stood the test of time, but the way we write, maintain, and
evolve RPG code doesn’t have to stay stuck in the 1990s. As a manager of IBM i
developers, I’m constantly asking: How can we modernize how we work—without
rewriting everything?
That’s where AI and automation come in.
Let’s be clear: AI won’t replace your RPG developers. But it can
supercharge their productivity and help them stay focused on value-added work.
Tools That Actually Help RPG Developers
Here are some real-world tools and examples of how AI and automation are
showing up in RPG workflows today:
1. ChatGPT + Claude: Legacy Code Interpreter & Assistant
AI models like ChatGPT (OpenAI) and Claude (Anthropic) are
game-changers for RPG. With a clear prompt, you can:
- Summarize large blocks of legacy
RPG or CL code.
- Explain obscure business logic.
- Translate RPG II or III to
free-format RPG.
- Generate documentation or
comments.
- Even simulate a peer review.
Example Prompt:
“Explain this RPG program to a new developer. Highlight any data
validation and external calls.”
You’ll get a clean breakdown that you can use in onboarding,
documentation, or even your own understanding.
2. GitHub Copilot + VS Code: Smarter Coding and Snippets
While Copilot doesn’t natively support RPG out of the box, you can
integrate RPG syntax highlighting into VS Code and train Copilot
through usage. It becomes surprisingly good at:
- Recommending CL snippets.
- Filling out RPG subroutines with
consistent logic.
- Generating shell test cases or
SQL statements.
Pro Tip: Use Copilot when you’re writing modern code (SQL, JavaScript, or service
programs that wrap RPG functions). It's incredibly helpful for APIs, UI logic,
or SQL joins.
3. RDi Automation + Templates
You can use automation inside RDi to:
- Auto-fill common field
definitions or copy members.
- Create templates for common
programs like report drivers or invoice validation routines.
- Integrate scripts for compiling, checking
object versions, or running regression test jobs.
This is low-hanging fruit for teams. A shared library of smart templates
can easily save 10–20 minutes per program—especially when onboarding
junior developers.
Why It Matters: Speed, Clarity, Focus
Here's the real win: focus. These tools eliminate boilerplate and
cognitive overload. Instead of staring at a 5,000-line RPG program, your
developer starts with a summary and some suggested fixes. Instead of guessing
at business logic buried in indicators, you generate a quick outline and review
it with a business analyst.
That’s not just faster. That’s smarter.
Start Small: One Workflow at a Time
If you're curious but cautious, here’s where I’d start:
- Use ChatGPT or Claude to
summarize one old RPG program per week.
- Add GitHub Copilot to VS Code and
try it for SQL or CL snippets.
- Build one RDi snippet or compile
macro per team member.
You don’t have to overhaul your process. Just give your team a boost
where it matters most—in speed, clarity, and energy.
My Final Sips: The Human Touch Still
Matters
As I wrap up the day, sipping the last of my Cariboo Lakeshore Blend,
I remind myself: these tools aren’t here to replace what we do—they’re here to amplify
it.
RPG developers are stewards of decades of business logic. When we pair
that deep expertise with the right tools, we unlock the next level of
impact—cleaner code, clearer documentation, faster onboarding, and more room
for innovation.
Here’s to coffee, code, and continuous improvement.
Comments
Post a Comment