Dealing with legacy code, or as I fondly refer to it, “Classic” code, is an enduring challenge in the realm of software development. Every organization or software stack inevitably encounters code that screams for an update. However, some of this code has aged into what can only be described as museum-worthy artifacts.

The issue at hand is that classic code is now posing a significant problem. New programmers are either reluctant to engage with it or find themselves unable to comprehend its intricacies. This has led to a pronounced skills gap, with a scarcity of proficient programmers available to tackle the monumental task at hand. The demand for coding far surpasses the available expertise by a staggering factor of 1000x. The reliance on AI to bridge this gap seems like a distant possibility, at least for the foreseeable future.

Despite the challenges posed by classic code, it remains a steadfast presence. The pressing question then becomes: how do we navigate this landscape, especially if modernization initiatives were generously funded and businesses prioritized this critical issue? Classic code was crafted using limited toolsets and outdated data models, making deciphering and enhancing its business logic a formidable task. The complexity of this outdated code makes it less appealing for younger programmers who have been schooled in more advanced methodologies and practices.

The reality is that legacy, or classic, code is here to stay for the foreseeable future. This is a problem.

#code #legacy #modernization #rpg #ibmi #software #programming #refactoring #rpgle #codecrisis