COBOL, which dates back to the 1950s, still persists in mission-critical legacy systems that are only half understood by the companies that rely on them. Now experts are thinking of new ways to approach the problem of COBOL and develop the skills needed to work with it.
Josh Fruhlinger at InfoWorld says this skills gap is neither as extreme nor as straightforward as you might imagine.
Read more at InfoWorld.
Comments