Yes, I am a technophobe in the strictest sense of the definition, with an emphasis on the word "new." I don't trust anything that hasn't been proven. Of course, it wasn't always that way. I embraced computers early on. As an engineering student in 1974, my interaction with computers was via punch cards, and you counted lines of codes by the thickness of your card deck. In 1983,1 wrote a program for my U.S. Air Force Boeing 707 squadron to automate the chore of computing navigation and fuel logs and I thought that was great until we discovered an error in one of my lines of code. My mistake impacted all four of our squadron's airplanes. In 2004, another software error in an air traffic control computer impacted 800 airplanes. As aircraft become more and more dependent on computers, the result of a "software glitch" becomes harder and harder to predict. If an airplane is completely airworthy when flying on one side of a line of longitude, how could an imaginary line in space prevent it from flying according to specs on the other? Or how about another airplane whose electrical system now has a calendar-based limitation? Examining a few examples where these glitches were thought to be unpredictable can help us better prepare ourselves for what we cannot possibly foresee.
展开▼
