A few years ago, I posted about the Air Force’s abandoned $1 billion effort to consolidate all its many accounting systems. Now it appears the State of California is going through similar difficulties: State officials have failed to remedy problems that have contributed to a two-year delay for a new computer system and cost increases […]
Over at Kotaku, a Gawker Media web portal that covers computer games (a bigger industry than Hollywood, I might point out), Jason Schreier has an excellent article outlining the fall of LucasArts, once one of the most productive and successful video game companies around, but now no longer in existence. It is worth a careful […]
Vernor Vinge, in several of his science fiction novels (such as A Fire upon the Deep), posits the existence of “zones of thought” within the inner portion of our galaxy that place inherent limits on intelligence and technology — the further you get from the galaxy’s center, the greater intelligence and technology is possible. The […]
Classic patterns in disputed IT project: Hertz v. Accenture
Just ran across this article at the always-irreverent-but-usually-spot-on Register, an IT news site out of England. The standard patterns of a troubled IT project are so evident in this one report that I may well use it as a case study for my CS 428 (“Real-world software engineering”) class this fall. Here are some of […]
Neverending Story pattern: School District ERP system late, over-budget
A story a few days ago caught my eye, not because it was unusual, but because it follows so familiar a pattern. Here are a few excerpts from the article: MANATEE — Late nights, hefty contracts and humming computers are a norm in the district’s School Support Center, where employees are working to fix a […]
Minnesota DMV software project: Faulty Towers/Neverending Story patterns
In my 2000 white paper, “Patterns in IT Litigation: System Failure (1976-2000)” [PDF], which I researched and wrote while at PricewaterhouseCoopers, I describe six broad fact patterns to classify the types of software system implementation failure. One of those patterns I named “Faulty Towers”: The client buys the system from [or has the system developed […]
![The Meltdown/Spectre CPU bugs: a dramatic global case of the “Unintended Consequences” pattern [UPDATED 4/4/18]](http://bfwa.com/wp-content/uploads/2018/01/intel-cpu-150x150.jpg "The Meltdown/Spectre CPU bugs: a dramatic global case of the “Unintended Consequences” pattern [UPDATED 4/4/18]")
Back in 2000, PricewaterhouseCooper published my research white paper, “Patterns in IT Litigation: Systems Failure (1976-2000)” (PDF). This paper reflected research I and my staff had done over several months on roughly 120 two- or three-party lawsuits involving information technology. I found that almost all of these lawsuits fell into one or two of six […]