This isn't a huge issue if needlessly obtuse code is bringing down your epic Ruth Bader Ginsburg fanfic, On The Basis Of Sex (In The f****n' Sense). But spaghetti code has been blamed for things like a lethal car crash caused by a car's flawed acceleration system, a six-hour 911 outage in the entire state of Washington, United Airlines having to ground its whole fleet for a day, and New York Stock Exchange trading going down like it had been targeted by a Batman villain.
Every program breaks sometimes, but modern code has become so large and sprawling that it's impossible to test, or even understand, every possible situation and variable. How do you anticipate every outcome in a system designed for millions of people? And when code breaks, it's not like when we broke our arm trying to do that backflip -- the problem cannot be visually diagnosed. You're stuck staring at tens of millions of badly organized and documented lines of code, trying to figure out what went wrong.
Programming's not exactly a new skill anymore, but the codes -- and the systems they power -- are getting bigger. National services, entire cars. And new innovations provide new ways to fail. No, we're not saying that society is going to collapse in a Skynet-style catastrophe, but the fact that your car might crash because some programmer didn't follow their style guide is even weirder.