'IT'S NOT A BUG, IT'S A FEATURE.' TRITEā€”OR JUST RIGHT?

WE’LL NEVER KNOW who said it first, nor whether the coiner spoke sheepishly or proudly, angrily or slyly. As is often the case with offhand remarks that turn into maxims, the origin of It’s not a bug, it’s a feature is murky. What we do know is that the expression has been popular among programmers for a long time, at least since the days when Wang and DEC were hot names in computing. The Jargon File, a celebrated lexicon of hacker-speak compiled at Stanford in 1975 and later expanded at MIT, glossed the adage this way:

A standard joke is that a bug can be turned into a feature simply by documenting it (then theoretically no one can complain about it because it’s in the manual), or even by simply declaring it to be good. “That’s not a bug, that’s a feature!” is a common catchphrase.

10/9/2018

When 19th-century inventors and engineers started using bug as a synonym for defect, they were talking about mechanical ­malfunctions, and mechanical malfunctions were always bad. The idea that a bug might actually be something desirable would never have crossed the mind of an Edison or a Tesla. It was only after the word entered the vocabulary of coders that it got slippery. It’s not a bug, it’s a feature is an acknowledgment, half comic, half tragic, of the ambiguity that has always haunted computer programming.

In the popular imagination, apps and other programs are “algorithms,” sequences of clear-cut instructions that march forward with the precision of a drill sergeant. But while software may be logical, it’s rarely pristine. A program is a social artifact. It emerges through negotiation and compromise, a product of subjective judgments and shifting assumptions. As soon as it gets into the hands of users, a whole new set of expectations comes into play. What seems an irritating defect to a particular user—a hair-trigger ­toggle between landscape and portrait mode, say—may, in the eyes of the programmer, be a specification expertly executed.

Who can really say? In a 2013 study, a group of scholars at a German university sifted through the records of five software projects and evaluated thousands of reported coding errors. They discovered that the bug reports were themselves thoroughly buggy. “Every third bug is not a bug,” they concluded. The title of their paper will surprise no one: “It’s Not a Bug, It’s a Feature.”

INABIAF—the initialism has earned a place in the venerable Acronym Finder—is for programmers as much a cri de coeur as an excuse. For the rest of us, the saying has taken on a sinister tone. It wasn’t long ago that we found software ­dazzling, all magic and light. But our perception of the programmer’s art has darkened. The friendly-seeming apps and chatbots on our phones can, we’ve learned, harbor ill intentions. They can manipulate us or violate our trust or make us act like jerks. It’s the features now that turn out to be bugs.