<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Legacy-Systems - Tag - vo.rs</title><link>https://vo.rs/tags/legacy-systems/</link><description>Legacy-Systems - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Fri, 30 May 2025 13:15:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/legacy-systems/" rel="self" type="application/rss+xml"/><item><title>Rebooting Legacy Systems: Modernising COBOL Without Breaking Compliance</title><link>https://vo.rs/story/rebooting-legacy-systems-modernizing-cobol-without-breaking-compliance/</link><description>&lt;p&gt;Somewhere in a bank right now, a COBOL program written before the person maintaining it was born is settling a payment. It has run every night for forty years, it has never been fully understood by anyone currently employed, and it processes a volume of money that makes the idea of &amp;ldquo;just rewriting it&amp;rdquo; the sort of joke that gets people fired. COBOL turns out to be one of the most quietly durable technologies ever built: code compiled in the 1970s still runs unmodified on IBM&amp;rsquo;s current z16 mainframe, because IBM has held backward compatibility across every hardware generation since. That durability is exactly the trap. The systems work, so no one touches them, so the knowledge of how they work leaks away one retirement at a time, until you are left with a black box that mints money and terrifies auditors.&lt;/p&gt;</description><pubDate>Fri, 30 May 2025 13:15:00 +0000</pubDate></item></channel></rss>