Flylib.com

Books Software

 
 
 

What Do You Get When You Cross a Computer with a Warship?


What Do You Get When You Cross a Computer with a Warship?

In September 1997, while conducting fleet maneuvers in the Atlantic, the USS Yorktown , one of the Navy's new Aegis guided-missile cruisers, stopped dead in the water. A Navy technician, while calibrating an on-board fuel valve, entered a zero into one of the shipboard management computers, a Pentium Pro running Windows NT. The program attempted to divide another number by that zero—a mathematically undefined operation—which resulted in a complete crash of the entire shipboard control system. Without the computers, the engine halted and the ship sat wallowing in the swells for two hours and 45 minutes until it could be towed into port. Good thing it wasn't in a war zone.

graphics/01inf05.gif

What do you get when you cross a computer with a warship? Admiral Nimitz is rolling in his grave! Despite this setback, the Navy is committed to computerizing all of its ships because of the manpower cost savings. To deflect criticism of this plan, it blamed the "incident" on human error. Because the software-creation process is out of control, the high-tech industry must bring its process to heel, or else it will continue to put the blame on ordinary users while ever-bigger machines sit dead in the water.


Techno-Rage

An article in the Wall Street Journal once described an anonymous video clip circulated widely by email that showed a "[m]ustachioed Everyman in a short-sleeved shirt hunched over a computer terminal, looking puzzled. Suddenly, he strikes the side of his monitor in frustration. As a curious co-worker peers over his cubicle , the man slams the keyboard into the monitor, knocking it to the floor. Rising from his chair , he goes after the fallen monitor with a final, ferocious kick."

The article went on to say that reaction to the clip had been " intense " and that it had apparently tapped into "a powerful undercurrent of techno-rage."

graphics/01inf06.jpg

It's ironic that one needs to be moderately computer savvy to even send or view this video clip. The man in the video may well be an actor, but he touches a widespread, sympathetic chord in our business world. The frustration that difficult and unpleasant software-based products are bringing to our lives is rising rapidly .

Joke emails circulate on private email lists about "Computer Tourette's." This is a play on the disorder known as Tourette's syndrome, some of whose sufferers engage in uncontrollable bouts of swearing . The joke is that you can walk down the halls of most modern office buildings and hear otherwise -normal people sitting in front of their monitors , jaws clenched, swearing repeatedly in a rictus of tense fury. Who knows what triggered such an outburst: a misplaced file, an inaccessible image, or a frustrating interaction. Or maybe the program just blandly erased the user 's only copy of a 500-page manuscript because he responded with a Yes to a confirmation dialog box, assuming that it had asked if he wanted to "save your changes" when it actually asked him if he wanted to "discard your work."


An Industry in Denial

We are a world awash in high-tech tools. Computers dominate the workplace and our homes , and vehicles are filling up with silicon- powered gadgets. All of these computerized devices are wildly sophisticated and powerful, but every one of them is dauntingly difficult and confusing to use.

The high-tech industry is in denial of a simple fact that every person with a cell phone or a word processor can clearly see: Our computerized tools are too hard to use. The technologists who create software and high-tech gadgets are satisfied with their efforts. The software engineers [1] who create them have tried as hard as they can to make them easy to use, and they have made some minor progress. They believe that their products are as easy to use as it is technically possible to make them. As engineers, their belief is in technology, and they have faith that only some new technology, such as voice recognition or artificial intelligence, will improve the user 's experience.

[1] Throughout the computer industry, the term "software engineer" is used synonymously with the term "programmer"; throughout this book, I have done the same.

Ironically, the thing that will likely make the least improvement in the ease of use of software-based products is new technology. There is little difference technically between a complicated, confusing program and a simple, fun, and powerful product. The problem is one of culture, training, and attitude of the people who make them, more than it is one of chips and programming languages. We are deficient in our development process , not in our development tools.

The high-tech industry has inadvertently put programmers and engineers in charge, so their hard-to-use engineering culture dominates. Despite appearances , business executives are simply not the ones in control of the high-tech industry. It is the engineers who are running the show. In our rush to accept the many benefits of the silicon chip, we have abdicated our responsibilities. We have let the inmates run the asylum .

When the inmates run the asylum, it is hard for them to see clearly the nature of the problems that bedevil them. When you look in the mirror, it is all too easy to single out your best features and overlook the warts. When the creators of software-based products examine their handiwork, they overlook how bad it is. Instead, they see its awesome power and flexibility. They see how rich the product is in features and functions. They ignore how excruciatingly difficult it is to use, how many mind-numbing hours it takes to learn, or how it diminishes and degrades the people who must use it in their everyday lives.