Blue Toyotas of Death
- February 23, 2010
- News, Politics
- Leave a Comment
What happens when your computer crashes? You get ticked off, probably spew a few four-letter words, then turn it off and turn it back on. In most cases, the system comes back up and you’re good to go.
Now, what happens if your car’s computer crashes?
Rep. Henry Waxman sent a terse letter to Transportation Secretary Ray LaHood, complaining that the National Highway Traffic Safety Administration doesn’t have the expertise to properly evaluate technical problems in cars, such as those that have plagued Toyota:
According to some accounts, autos now contain more computer code than some fighter jets, nearing 100 million lines of code. Yet, NHTSA officials told the Committee staff that the agency does not employ any electrical engineers or software engineers. As a result, NHTSA appears to lack the technical expertise necessary to analyze whether incidents of sudden unintended acceleration are caused by defects in the cars’ electronic systems.
Waxman makes a good point. Cars and trucks today have extremely sophisticated computers, and a software defect can cause all kinds of problems. And yet apparently there’s no real government oversight when it comes to all that code.
Jesus Diaz of Gizmodo wrote a great essay a while back about the “beta” culture that has become the norm in the technology world:
I’m tired of this. This sense of permanent discomfort with the technology around me. The bugs. The compromises. The firmware upgrades. The “This will work in the next version.” The “It’s in our roadmap.” The “Buy now and upgrade later.” The patches. The new low development standards that make technology fail because it wasn’t tested enough before reaching our hands. The feeling now extends to hardware: Everything is built to end up in the trash a year later, still half-baked, to make room for the next hardware revision. I’m tired of this beta culture that has spread like metastatic cancer in the last few years, starting with software from Google and others and ending up in almost every gadget and computer system around. …
Clearly, the problem is the development process and the time to market, with product cycles shortened and corners cut to keep a continuous stream of cash flowing in. The rush to feed these cycles with increasingly more complex engineering seems to be at odds with shortened development and quality assurance processes, resulting in beta-state first-generation products. This beta culture, the same one that already plagues the web, breeds people who are willing to accept bugs in the name of cutting-edge gear.
Diaz was clearly talking about consumer electronics and the Internet, but the same arguments can be applied to auto manufacturers, who face the same market pressures that any other technology company does: produce more complex, more capable, and yet more efficient products year after year at a lower cost and market the hell out of them to gain whatever slight edge you can over your competitors.
If you’re talking a website or a computer operating system or a smartphone, manufacturers can probably afford to cut corners in the development cycle if they know most bugs can be patched later. After all, in the vast majority of cases a software failure is at most an inconvenience and an annoyance. But a software failure in a car can — and does — endanger lives.
It’ll be interesting to see how Toyota and other auto makers respond to these issues. Hopefully they can improve the quality control on their own, but I’m willing to bet the government will also have lots to say. It usually does.
Previously:
What the auto mileage bill really means for consumers


















