10 Facts About Software bug

Term "Software bug" to describe defects has been a part of engineering jargon since the 1870s and predates electronics and computers; it may have originally been used in hardware engineering to describe mechanical malfunctions.

Isaac Asimov used the term "Software bug" to relate to issues with a robot in his short story "Catch That Rabbit", published in 1944.

Term "Software bug" was used in an account by computer pioneer Grace Hopper, who publicized the cause of a malfunction in an early electromechanical computer.

Hopper was not present when the Software bug was found, but it became one of her favorite stories.

One argument is that the word "Software bug" is divorced from a sense that a human being caused the problem, and instead implies that the defect arose on its own, leading to a push to abandon the term "Software bug" in favor of terms such as "defect", with limited success.

Related searches

Software bug engineering applies many techniques to prevent defects.

Sometimes, a Software bug is not an isolated flaw, but represents an error of thinking or planning on the part of the programmer.

One cause of the Therac-25 radiation machine deaths was a Software bug that occurred only when the machine operator very rapidly entered a treatment plan; it took days of practice to become able to do this, so the Software bug did not manifest in testing or when the manufacturer attempted to duplicate it.

Releases that emphasize Software bug fixes are known as maintenance releases, to differentiate it from major releases that emphasize feature additions or changes.

Possibly the most famous Software bug is the Year 2000 problem or Y2K Software bug, which caused many programs written long before the transition from 19xx to 20xx dates to malfunction, for example treating a date such as "25 Dec 04" as being in 1904, displaying "19100" instead of "2000", and so on.