COBOL

COBOL. An "old" programming language that has been rumoured to be replaced for years now. But how do you do that? Alternatives aren’t always as stable as COBOL, one migration process after another having failed in recent times. In the meanwhile, little attention is paid to upholding COBOL knowledge. After all, why bother with a language that will be obsolete in a few years?

But what if replacing COBOL fails in the short run?

What if COBOL isn’t replaced as soon as planned or desired, but you do notice your COBOL department dwindling? What do you do to keep existing expertise, while continue to be ready for the future? This can be done by deploying Calco MasterClass Professionals. These are young, analytically strong people with ambition, drive and the will to learn COBOL. Because they are young, they can absorb a new language quickly. So, let’s say you need to keep COBOL expertise in-house, because systems are still running on COBOL. You, however, also want to be future-proof. The answer: young professionals. These ensure that the critical systems continue to run while maintaining flexibility for the future.

What do you do to keep existing expertise, while continue to be ready for the future?