From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] Origin of "bug" (was: Grace Hopper)
Date: Sun, 10 Dec 2017 10:41:17 +1100 [thread overview]
Message-ID: <20171209234117.GG78437@eureka.lemis.com> (raw)
In-Reply-To: <alpine.BSF.2.21.1712101004450.35694@aneurin.horsfall.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1939 bytes --]
On Sunday, 10 December 2017 at 10:17:54 +1100, Dave Horsfall wrote:
> On Sat, 9 Dec 2017, arnold at skeeve.com wrote:
>
>>> She coined the term "debugging" when she extracted a moth from a set of
>>> relay contacts from a computer (the Harvard Mk I) and wrote "computer
>>> debugged" in the log, taping the deceased Lepidoptera in there as well.
>>
>> See https://en.wikipedia.org/wiki/Debugging#Origin_of_the_term which
>> indicates that "bug" and "debugging" had been around as technical terms
>> long before that incident.
>
> I need to investigate that further (I'd hate to spread misinformation,
> which is why I enjoy being corrected, esp. in public).
I was going to pipe up here, but I wasn't sure if it would be
interesting. The Oxford English Dictionary has a first reference to
in this sense in 1875:
5. orig. U.S.
a. A defect or fault in a machine (esp. an electrical or electronic
one), or in a process, etc.
1875 Operator 15 Aug. 5/1 The biggest âbugâ yet has been discovered
in the U.S. Hotel Electric Annunciator.
1889 Pall Mall Gaz. 11 Mar. 1/1 Mr. Edison, I was informed, had
been up the two previous nights discovering âa bugâ in his
phonographâan expression for solving a difficulty, and
implying that some imaginary insect has secreted itself inside
and is causing all the trouble.
Grace Hopper's bug doesn't get a mention.
Greg
--
Sent from my desktop computer.
Finger grog at lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171210/555e472b/attachment-0001.sig>
next prev parent reply other threads:[~2017-12-09 23:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 23:26 [TUHS] Grace Hopper Dave Horsfall
2017-12-09 0:05 ` Larry McVoy
2017-12-09 0:39 ` Mike Markowski
2017-12-09 3:21 ` Dave Horsfall
2017-12-09 10:04 ` Jason Stevens
2017-12-09 17:31 ` Paul Winalski
2017-12-09 20:03 ` Lyndon Nerenberg
2017-12-09 18:03 ` arnold
2017-12-09 23:17 ` Dave Horsfall
2017-12-09 23:41 ` Greg 'groggy' Lehey [this message]
2017-12-10 0:30 ` [TUHS] Origin of "bug" (was: Grace Hopper) Bakul Shah
2017-12-10 3:20 ` Greg 'groggy' Lehey
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=20171209234117.GG78437@eureka.lemis.com \
--to=grog@lemis.com \
/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).