Legacy system

"Legacy" is used loosely in the industry, often as a polite way of saying outdated. Applied to mainframe systems, the label hides something more interesting.

A typical mainframe application has been in production for thirty or forty years. In that time it has absorbed every regulatory change, every edge case, every strange-but-real business rule the organisation has encountered. The code is not old because nobody cared; it is old because it works, and because the cost and risk of rewriting a system that moves millions of payments a day is enormous.

That is why replacement projects so often stall. The difficulty is rarely the technology. It is that nobody has a complete written description of what the system actually does. The code is the specification.

This is where the opportunity sits. The organisations running these systems need people who can read the code, understand the business rules inside it, and keep it running or carefully modernise it. That skill is in short supply and getting shorter.