Local RPG Development
Your source is on your machine and the compile is on the partition. The same program, compiled and running its green screen without one, until the object you finally ship.
Read the articleUnit Testing RPG
Unit tests for your RPG programs, two ways: with RPGUnit on the IBM i, or with JUnit and GitHub Actions - no IBM i in the pipeline. Working code for both.
Read the articleExposing Your AS/400 as a REST API
Your RPG programs, serving a REST API from ordinary servers - while your green screens, batch jobs, and data stay right where they are. No middleware. No rewrite.
Read the article