From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: ***
X-Spam-Status: No, score=3.4 required=5.0 tests=BAYES_50,INVALID_DATE,
	MSGID_SHORT,REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no
	version=3.4.4
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ucla-cs!levin
From: levin@CS.UCLA.EDU
Newsgroups: comp.lang.ada,comp.lang.apl,comp.lang.forth
Subject: Collecting favorite bug stories
Message-ID: <3667@curly.ucla-cs.UCLA.EDU>
Date: Sat, 10-Jan-87 03:27:34 EST
Article-I.D.: curly.3667
Posted: Sat Jan 10 03:27:34 1987
Date-Received: Sat, 10-Jan-87 06:36:32 EST
Sender: root@ucla-cs.UCLA.EDU
Reply-To: levin@CS.UCLA.EDU (Stuart Levine)
Distribution: world
Organization: UCLA Computer Science Department
Xref: mnetor comp.lang.ada:100 comp.lang.apl:16 comp.lang.forth:34
List-Id: <comp.lang.ada>

I am collecting anecdotes of experiences, (real or imagined) 
for a book to be titled:

    MY FAVORITE BUGS: Humourous, and Horrible Experiences in Software
                      Engineering.

As one might tell from the title, the book will be filled with wonderful
tales that programmers tell each other, over a few too many beers,
after a long day at the keyboard.

The book is meant to be read for entertainment, as well as for education. 
In that light, I am asking that contributions include (when possible),
a short description of the bug, some comments on why it was special,
how the solution was found, and maybe (for the appendix of the book)
a few lines of code.

You don't need to write anything long; a page should do it.  All
contributors are thanked in advance, and will be credited in the book
for their contributions.

Soon in a bookstore near you...
(apologies if you see this message on ten different newsgroups)

Stuart LeVine