I was going to write more about the current crash-fest in computerized things, but the pundits have beaten me to it. Short version: AI keeps finding vulnerabilities (or claiming to -- look, AI still tends to tell people what they want to hear), organizations keep trying to plug them, and, um. Some of those fixes are boxes full of vibe-coded glitches.
And why is that? There's the real story: At the heart of many businesses, you will find old hardware, running software that is often even older, stuff written for operating systems and dead(ish) languages that ran on mainframes and the original "minicomputers," a six-foot rack or two of electronics, emulated on slightly newer (call it late DOS-era X86s or early Windows) hardware. People who really, deeply get that kind of programming were never terribly common, truly gifted troubleshooters of it even less so, and one of the core talents was what chessplayers call "sitzfleisch:" the ability to park one's backside in a chair and concentrate on the task at hand for genuinely unreasonable amounts of time. Who does that now? Hardly anyone. And a lot of the old code is patches on patches on fairly wild improvisations that let ancient systems hand data off to modern networks and get input from them.
Sometimes trying to fix it breaks it. And most of it is only still there because jacking up the enterprise it supports -- a bank, or a factory or a subway, etc. -- and driving a whole new, modern system in under it, while it's all running, is nearly impossible. They're better off (at least for this quarter -- and for a publicly-traded company, they're not even supposed to be looking much farther ahead; government stuff can be even worse) just patching the patches, even when it coughs and falls over. It turns out that beating a dead horse until it softens and stuffing it into a powered exoskeleton will work, especially if you don't mind the smell.
"Whoa, Nelly?" Better not. Your paycheck is in that cart it is hauling, along with your airline tickets, your retirement savings and your Social Security.
Update
1 year ago

No comments:
Post a Comment