The December 2022 issue of IEEE Spectrum is here!

Close bar

Last week, I blogged about the continuing IT woes in California. Well, the LA Times had another California IT story this week that reports some 117,000 Californians have been without their unemployment checks because the state's computers haven't finished being programmed to handle the extensions in unemployment insurance authorized by the federal government on the 6th of November.

The LA Times says that, "State Employment Development Department officials say they are doing everything they can to issue the checks, even postponing some staff furloughs to deal with the demand for services. But they say the state's 30-year-old computer system isn't programmed to recognize the extensions, requiring technicians to write new code."

California is hoping to start issuing the checks next week, although this may be optimistic. 

California's Employment Development Department admits that it is rushing to reprogram its computers which usually means an unexpected problem is likely to crop up.

"We're trying to fully upgrade the system as it's moving at a record pace, while being very careful to not risk shutting down the rest of the system," an Employment Development Department  spokesperson was quoted as saying in the Times' article.

I have noted previously over this year (e.g., here, here and here) some of the on-going problems other states have been having with their unemployment insurance systems. There is an excellent updated overview of these problems across the US here at CivSource.

And in a related development, the US Department of Agriculture is warning states not to outsource their food stamp programs, and article in the Statesman reports.

The USDA sent a letter out to state governments on the 20th of November which stated,  "These projects encountered severe problems in meeting critical performance standards and many eligible (food stamp) applicants have suffered as a result... We do not support furtherance of such projects, and believe that they put public funds and our clientele at risk."

This places the states in a very uncomfortable quandary. Their IT systems are aging and fragile, and pose major operational risk. But the states are also being told by the Federal government that outsourcing their IT operations isn't recommended either because that poses unacceptable risk as well.

Not a good situation at all.

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
Vertical
A plate of spaghetti made from code
Shira Inbar
DarkBlue1

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less
{"imageShortcodeIds":["31996907"]}