Why RPG Programmers Seem Hard to Find
A few years back, some tech bloggers bemoaned the lack of experienced RPG programmers. They claimed that IBM i programmers were aging out with the system. In response, others said, “There’s no lack of iSeries RPG Developers.” IBM might be “old,” but it’s one of the most used and reliable systems in business.
Furthermore, its code has evolved over the years, from proprietary to open, from a frozen structure to ILE , from RPG language to RPG “free form.” In short, IBM adapted its code and OS over its existence, which preserved its dominance. That evolution allowed for transitions from legacy systems to where it is at present, largely adaptable in the RPG free form. It was a smart move on IBM’s side since younger programmers were at college learning the latest programming languages.
It is cleaner, modularized, and co-exists with languages in the open world. Its evolution is what makes it possible for younger programmers with the right coding skills sets (and good minds) to become experts in RPG.
The Advanced Skills of RPG Programmers
An RPG programmer enjoys a variety of challenges, from creating specialized software in the language to maintaining, fixing or updating older RPG programs. So, does an expert need to know the legacy code? Yes. Imagine the codes looking like the differences between modern dialects.
Each business has been specializing its software for as long as it’s used IBM systems. Differences in modern free form RPG, might be like deciphering English in Australia versus Britain versus the USA.
ILE and earlier AS400 code might be comparable to a language expert like Middle English, almost nothing like the modern tongue. Translations will be needed and the quality of each generation’s coding matters.
RPG programmers are working across time, across business cultures, and structures. When they analyse, maintain, design and develop to meet what a company needs, they need skills with RPG, RPG ILE, RPG-FREE and SQL. They create or enhance programs.
They create technical documentation or pseudo code for themselves or programmers who follow them. They troubleshoot business processes, including looking for database issues. They identify the best syntax checkers, monitor, and debug current software. They use the best change management techniques. They advise businesses on how to improve processes.
Ninjas, Evolutionists, Architects, Carpenters, and Programmers
The best RPG programmers are ninjas of the tools and languages. They understand their language well, but can integrate with CL, SQL, JAVA, C#, XML, JSON, HTML, PHP, and other code. Because IBM’s strength lays in part with its compatibility.
The best RPG programmers are evolutionists. They refactor, tinker, and upgrade legacy RPG into /free format. As technology evolves, they keep their skills up-to-date and be agile for new demands.
The best RPG programmers are architects. They work with the aesthetic clarity of modern code and design software with modules, directories, and service programs that are reusable.
The best RPG programmers are carpenters. Just as a carpenter measures twice and cuts once, programmers make it right before they make it faster. They know how the logic cycle works, but use clean /free form code. Just as a skilled carpenter works efficiently and makes clear marks, so also programmers create pseudo code and documentation to preserve the quality and longevity of programs.