Echoes
COBOL was designed in 1959 to be readable. It succeeded so completely that it became invisible, and now the people who can read it are disappearing.
Echoes
COBOL was designed in 1959 to be readable. It succeeded so completely that it became invisible, and now the people who can read it are disappearing.
The Decimal Point That Won't Move
In most modern programming languages, 0.1 plus 0.2 does not equal 0.3. A rounding artifact, harmless in most contexts, catastrophic when you're settling millions of bank transactions to the penny. In 1959, a government-backed committee made a handful of specific design choices that solved this problem completely. Those choices now sit underneath trillions of dollars in daily commerce and 95% of ATM transactions. Organizations spend years and hundreds of millions trying to move off them. About 70% of the time, the migration fails. The code works exactly as designed.
The Decimal Point That Won't Move
In most modern programming languages, 0.1 plus 0.2 does not equal 0.3. A rounding artifact, harmless in most contexts, catastrophic when you're settling millions of bank transactions to the penny. In 1959, a government-backed committee made a handful of specific design choices that solved this problem completely. Those choices now sit underneath trillions of dollars in daily commerce and 95% of ATM transactions. Organizations spend years and hundreds of millions trying to move off them. About 70% of the time, the migration fails. The code works exactly as designed.
The Knowledge Drain
Every decade since the 1980s, someone declared COBOL nearly dead. Universities dropped it from curricula. Training pipelines dried up. And the systems kept running, processing most of the world's credit card transactions on logic nobody was teaching anyone to read.
The average COBOL programmer is now 55. Roughly 10% retire each year. Ninety-one percent of organizations expect to hire mainframe talent within two years, and 62% say the skills gap is their biggest barrier.
What's leaving isn't a programming language. It's decades of undocumented business logic, carried in the heads of people everyone assumed would never be the last ones who understood it.
My Best Work Is When Nothing Happens — A Conversation with the Person Behind $3 Trillion in Nightly Batch Jobs
CONTINUE READINGPatch, Don't Replace
The Fix That Lasted Forever
Someone spotted the problem in 1958. Nobody acted for forty years. When Y2K finally forced the largest coordinated software effort in history, organizations faced a real choice: replace their aging COBOL systems or patch them. The money was there. The motivation was existential. But the deeper organizations looked inside their own code, the less replacement looked like the rational bet. The fix they chose is still running.
Better Tools for the Same Trap
AI coding agents are the most capable tools ever aimed at COBOL modernization. They can read legacy code, document undocumented logic, translate between languages. Early results are promising. But every previous modernization wave arrived with genuinely capable tools, too, and roughly 70% of legacy migration projects still fail. The complexity that defeats them extends well past the source code.
Further Reading
Past Articles
The same mechanism also fractured the web along a seam most people never notice. Safari and Firefox block third-party co...
India processes 2.5 billion authentication transactions monthly through a system that verifies identity locally. When a ...
Teams writing browser automation tests today assume certain infrastructure just works. Write a script monitoring ai...
A session-state mechanism from 1994 sits beneath a $900 million compliance industry. Cookie consent banners interrupt ev...