|
![]() |
![]()
on writing bug reports |
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . |
The View From Here: Everybunny Needs Somebunny
April 1996
Sooner or later we all need help, whether it's with technical computer issues or Japanese ikibana (flower arranging). There is a community out there, the USENET world of newsgroups. There's even local flavor, several Sirius newsgroups and a large number of Bay Area newsgroups, including:
There are more, this is just a sampling. These aren't even the best of show, the for sale newsgroup is less directed than product-specific groups such as
misc.forsale.computers.mac-specific.portables
Seek and ye shall find, ask and it shall be given.
Oh yes, that's what I wanted to talk about today. Not about the existence of newsgroups, but about asking for help. Specifically about asking for help about technical issues.
I monitor the Sirius and Macintosh (comp.sys.mac.*) newsgroups, and I'm dismayed by the number of people who sincerely ask for help but do so in a manner that discourages assistance. I put the following on 29 September 1994 into my web pages, but I reproduce it here because it's as relevant today as ever, whether you're sending a bug report to the author of software, getting ready to call technical support, or posting a plea for assistance on a newsgroup.
I've been in the computer science field since 1979, when I stumbled across an Korean-war surplus Teletype model 33 in my high school guidance counsellor's office. It connected to a nearby university, which gave us all the computer time we could eat up running NCR BASIC.
I wrote my first computer program, Fibonacci numbers, shortly thereafter. It had a problem (no stopping condition) and I was introduced to bug reporting about one minute after loading the paper tape, downloading my program, and executing it.
A usable bug report (feature request, suggestion, etc.) will give the following information:
Please send one bug per bug report. Your feedback will be put into a bug database, and everything after the first bug will either be overlooked or require that someone read, understand, and carve up your multiple-bug message into small pieces. Do it yourself.
Just for grins I've included a bug report that I recently sent:
Hardware: Mac PowerBook 520c, 12mb RAM (max'd to 70mb)
Good day. I've just downloaded your program and find that it quits with an
error of 1 about one-half second after it comes up. If I do nothing MacOS
tells me of the error. If I jump in and grab the import text button I can
specify an html file before it goes away.
I've noticed in beta-testing other software tha the changes for the
blackbird-class powerbooks was non-trivial if you are making assumptions
about the system resoures (specifically WDEF 0) available to you.
Sorry I have nothing better to report. :-( M
|
Have you found errors nontrivial or marginal, factual, analytical and illogical, arithmetical, temporal, or even typographical? Please let me know; drop me email. Thanks! |