![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-300x200.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 […]
An earlier post here deal with allegations by Telsa that a former employee had stolen trade-secret information and taken it to a new startup. This latest article has a remarkably similar story, but involving an individual leaving Waymo and joining Uber: Uber has escaped a court order that could have effectively halted its self-driving car program, […]
From the article by Jordan Golson over at Verge: The complaint, filed in California Superior Court, County of Santa Clara, alleges that Anderson attempted to recruit at least 12 Tesla engineers to a new self-driving venture that he and Urmson were starting, in violation of Anderson’s non-solicitation agreement, and that Anderson took confidential Tesla information […]
From 2011 to 2013, I served as an expert witness in BanxCorp d/b/a BanxQuote v. Costco Wholesale Corporation et al., a copyright infringement case in the US District Court, Southern District of New York. To quote from the summary judgment opinion issued in this case by Judge Kenneth M. Karas (note — I have omitted […]
Cybercrime Review is one of the blogs I read daily, due to my ongoing interest in the intersection between law and technology. The posts generally have to do with court rulings and decisions in cases involving computer technology, such as whether someone can be compelled to provide a password for an encrypted data source. But […]
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 […]