Code is not an asset – it’s a liability. The longer a computer system has been running, the more tech debt it represents. The more important the system is, the harder it is to bring down and completely redo. Instead, new layers of code are slathered atop of it, and wherever the layers of code meet, there are fissures in which these systems behave in ways that don’t exactly match up. Worse still: when two companies are merged, their seamed, fissured IT systems are smashed together, so that now there are adjacent sources of tech debt, as well as upstream and downstream cracks:

pluralistic.net/…/dealer-management-software/#ant…

That’s why giant companies are so susceptible to ransomware attacks – they’re full of incompatible systems that have been coaxed into a facsimile of compatibility with various forms of digital silly putty, string and baling wire. They are not watertight and they cannot be made watertight. Even if they’re not taken down by hackers, they sometimes just fall over and can’t be stood back up again – like when Southwest Airlines’ computers crashed for all of Christmas week 2022, stranding millions of travelers:

pluralistic.net/2023/01/16/for-petes-sake/#unfair…

Airlines are especially bad, because they computerized early, and can’t ever shut down the old computers to replace them with new ones. This is why their apps are such dogshit – and why it’s so awful that they’ve fired their customer service personnel and require fliers to use the apps for everything, even though the apps do. not. work. These apps won’t ever work.