The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Rob Pike <robpike@gmail.com>
To: Dan Cross <crossd@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] 70th anniversary of (official) programming errors
Date: Wed, 16 Jun 2021 13:48:11 +1000	[thread overview]
Message-ID: <CAKzdPgyk_ZEojzXYLEHV1mPuybsap88fhCzZ-mE5JNukWFmDKQ@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W4cJX_4_965+hw4wUUDzxrW7enkeWGgxYdrobmzjN3SkA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1698 bytes --]

There are citations from Edison in the 19th century using the word, and a
quote somewhere by Maurice Wilkes about the stairwell moment when he
realized much of the rest of his life would be spent finding programming
errors.

That moth was not the first bug, nor the first "bug", it was the first
recorded "actual bug".

-rob


On Wed, Jun 16, 2021 at 9:46 AM Dan Cross <crossd@gmail.com> wrote:

> On Tue, Jun 15, 2021 at 6:55 PM John Cowan <cowan@ccil.org> wrote:
>
>> On Tue, Jun 15, 2021 at 6:25 PM Steffen Nurpmeso <steffen@sdaoden.eu>
>> wrote:
>>
>>> As not being hard-to-the-core i may have missed it, but also in
>>> 1951, in March, the wonderful Grace Hopper "conceives the first
>>> compiler, called A-O and later released as Math-Matic.  Hopper is
>>> also credited with coining the term 'bug' following an incident
>>> involving a moth and a Mark II.
>>>
>>
>> Yes, but wrongly.  The label next to the moth is "First actual case of
>> bug being found", and the word "actual" shows that the slang term already
>> existed then.  Brief unexplained faults on telephony (and before that
>> telegraphy) lines were "bugs on the line" back in the 19C.  Vibroplex
>> telegraph keys, first sold in 1905, had a picture of a beetle on the top of
>> the key, and were notorious for creating bugs when inexperienced operators
>> used them.  (Vibroplex is still in business, still selling its
>> continuous-operation telegraph keys, which ditt as long as you hold the
>> paddle to the right.)
>>
>
> Indeed, the Vibroplex key is called a "bug". I suspect this has something
> to do with its appearance more than anything else, though (it kinda sorta
> looks like, er, a bug).
>
>         - Dan C.
>
>

[-- Attachment #2: Type: text/html, Size: 3056 bytes --]

  reply	other threads:[~2021-06-16  3:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-15 22:16 Steffen Nurpmeso
2021-06-15 22:54 ` John Cowan
2021-06-15 23:44   ` Dan Cross
2021-06-16  3:48     ` Rob Pike [this message]
2021-06-16  4:13       ` Bakul Shah
2021-06-16 21:57         ` Steffen Nurpmeso
2021-06-18 20:19           ` John Cowan
2021-06-18 21:00             ` Steffen Nurpmeso
2021-06-18 22:59               ` Steffen Nurpmeso
2021-06-19 13:34               ` Harald Arnesen
2021-06-19 13:39                 ` Niklas Karlsson
2021-06-19  7:57             ` [TUHS] Bugs, Bööge and Bogeymen (was: 70th anniversary of (official) programming errors) Greg 'groggy' Lehey
2021-06-19 15:48               ` Steffen Nurpmeso
2021-06-19 15:52                 ` Niklas Karlsson
2021-06-19 16:36                   ` Steffen Nurpmeso
2021-06-19 21:05                 ` Harald Arnesen
2021-06-20  3:30                   ` arnold
2021-06-16  1:06   ` [TUHS] Bug etymology " Greg 'groggy' Lehey
2021-06-16  8:16 [TUHS] 70th anniversary of (official) programming errors Jason Stevens

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKzdPgyk_ZEojzXYLEHV1mPuybsap88fhCzZ-mE5JNukWFmDKQ@mail.gmail.com \
    --to=robpike@gmail.com \
    --cc=crossd@gmail.com \
    --cc=tuhs@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).