From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Bakul Shah <bakul@iitbombay.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] 70th anniversary of (official) programming errors
Date: Wed, 16 Jun 2021 23:57:13 +0200 [thread overview]
Message-ID: <20210616215713.f1CA8%steffen@sdaoden.eu> (raw)
In-Reply-To: <C964FEBE-BBE3-4A87-9F2F-E5C277053D85@iitbombay.org>
Bakul Shah wrote in
<C964FEBE-BBE3-4A87-9F2F-E5C277053D85@iitbombay.org>:
|> On Jun 15, 2021, at 8:48 PM, Rob Pike <robpike@gmail.com> wrote:
|> 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
|https://spectrum.ieee.org/the-institute/ieee-history/did-you-know-edison\
|-coined-the-term-bug
Interesting, thanks! 1947, then.
As you know well the BSD people dropped their calendar instead of
fixing it.
|Like Edison, she (Grace Hopper) was recalling the word’s older origins \
|in the Welsh bwg, the Scottish bogill or bogle, the German bögge, and \
(Only to clarify that „bögge“ is not a German word to the best of my
knowledge. I was looking, as it sounded so »northern«, there is
»Bodden« for example (a small bay with a very small aperture to
the sea), but no?)
|the Middle English bugge: the hobgoblins of pre-modern life, resurrected \
|in the 19th century as, to paraphrase philosopher Gilbert Ryle, ghosts \
|in the machine.
That not me. If me, then Schopenhauer. I also do not like the
Brainfuck language, for example. You know, if you have to go
somewhere ... In some Bhuddhistic monasteries, for example, monks
sit cross-legged in front of walls for hours each day. If you
really want, that will help, if you have learned the lesson.
Working in a kitchen garden is also advisable, you can reap.
|Electrical circuits can have "bad connections" so I do wonder if Edison \
|coined this word based on "ghost like" faults that magically appear \
|and disappear!
I seem to recall now that the bug story was clarified in the past
already? Now it is for me anyway, thank you all for that. I was
looking at BSD calendar mail and had a go.
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
next prev parent reply other threads:[~2021-06-16 21:58 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
2021-06-16 4:13 ` Bakul Shah
2021-06-16 21:57 ` Steffen Nurpmeso [this message]
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=20210616215713.f1CA8%steffen@sdaoden.eu \
--to=steffen@sdaoden.eu \
--cc=bakul@iitbombay.org \
--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).