US State Governments Can’t Shake IT Woes

Microsoft's inauspicious Windows RT 8.1 update, where did the term “glitch” come from?

2 min read
US State Governments Can’t Shake IT Woes

IT Hiccups of the Week

Most of the news involving last week’s IT-related problems, snarls and snags were once again drowned out by media stories concerning the recognition if not admission of major management blunders that led to the “glitches” in the Affordable Care Act website and its supporting systems. The Obama Administration now says that the two dozen or so major items on its IT “punch list” will be fixed and thoroughly tested within the next 33 days or so, but more than a few folks are willing to bet against that happening, especially in regard to the issue of data security.

Residents of California, Florida, Alaska, Pennsylvania, New Mexico, Kentucky, Michigan and Mississippi are among those fervently hoping that their states' ongoing government computer woes will be over by the end of November. However, I suspect that for many of those state residents, it will prove to be a forlorn hope as well.

US State Governments’ IT System Problems Persist

Unemployed Californian’s Continue to Complain of EDD Unemployment Computer System Problems

California Legislators Set Hearings into EDD System Troubles for Next Week

Florida’s New Connect Unemployment System Woes

Florida Trying to Fix New Connect Unemployment System

Alaska’s New Medicaid System Undergoing “Growing Pains”

Pennsylvania’s Worker’s Compensation System Problems Linger

New Mexico’s New Unemployment System Ops Improved, but Must Get Better

Kentucky Medicaid Billing System Problems Finally Clearing Up After Two Years

Call Volume Unusually High after Michigan Upgraded Unemployment System

Mississippi’s New Online Tax System Causing Headaches

Microsoft’s Less Than Smooth Windows RT 8.1 Update

Windows RT 8.1 Update Has Some “Show-Stopping” Installation Problems

Microsoft Pulls Windows RT 8.1 Update From Store

Microsoft  Fixes Windows RT 8.1 Update and Is Back in Store

What Does “Glitch” Exactly Mean?

A Brief Linguistic History of the Term “Glitch

Of Other Interest…

Facebook Suffers Worldwide Outage

Network Solution Experiences Outage for Third Time

US Customer and Border Protection Computer System Goes Offline

Cincinnati Bell Internet Goes Down

System Glitch Interrupts 911 Emergency Calls in Douglass County, Nebraska

Dallas Ft. Worth International Airport Traffic and Parking System Malfunctions Again

Nissan Recalling 152 000 SUVs for Anti-Lock Brake Software Upgrade

Credit Card System Problem Stiffing Washington, D.C. Taxi Drivers

Los Angeles Department of Works Computer Error Leads to Higher Water Bills

Schwab Trading Platform Experiences Problems after Integration with Third-Party System

Incompatible Hardware and Software Bring Beijing’s Subway Line 10 to a Halt

Photo: Ugurhan Betin/iStockphoto

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"]}