From 7a850dce9087b04f58946f49e2ae599e17d99e13 Mon Sep 17 00:00:00 2001 From: Jon Foster Date: Thu, 1 Apr 2021 07:03:29 -0700 Subject: [PATCH] Readme for "blunder" tracker --- README.md | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 README.md diff --git a/README.md b/README.md new file mode 100644 index 0000000..68f77cd --- /dev/null +++ b/README.md @@ -0,0 +1,27 @@ +Ye Ol' Pi Shack Blunder Tracking +================================ + +This is SysOp's place to keep track of blunders and wishes for the Ye +Ol' Pi Shack project. + +**NOTE:** The use of "Blunder", instead of "bugs", comes from two +places: + + 1. [Gary Kildall](https://computerhistory.org/blog/in-his-own-words-gary-kildall/) + in his book "Computer Connections", humurously points out, that + "errors" is not the right word for broken software (*bugs*) + since "error" in mathematical terms is a small percentage of + deviance from perfection. Most software "errors" take far more + effort to fix then it did to write them. Hence they should be + called "blunders". + + 2. [Grace Hopper](https://en.wikipedia.org/wiki/Grace_Hopper) is + attributed to first applying the term "bug" to computers. In the + photograph of her log (at that link) you will see its a physical + bug that had caused a physical, ie hardware, malfunction, not + software. Yes, the hardware malfunction caused the software to + malfunction, but the "bug" was still a hardware malfunction. + +So, you see, a "computer bug" is a hardware thing and problems with +software are too large to be considered "errors" so I'm using +Kildall's suggestion of "blunder". :-D