Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

gav (2710)

gav
  (email not shown publicly)
http://www.estey.com/
AOL IM: flufflegavin (Add Buddy, Send Message)

Hacker in NYC.

Journal of gav (2710)

Friday December 12, 2003
07:10 PM

how not to report bugs

[ #16316 ]

In an email from my boss:

C called to say that her boss, R, tried to place an order and it didn't work but then he tried again and it did. Can you look into it?

Arrrrgh!

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Tell your boss that's an intermittant failure. The recent solar flare activity has been causing significant electromagnetic pulses to be generated through the magnetosphere causing random bits to sometimes be flipped in CPUs. Until the sun calms down, we'll just have to deal with this. However, if you can get detailed bug reports listing exactly what the user did, you can find out what part of the CPU is being affected and route the code around it.

  • That looks very similar to every bug report that I have ever been given.
    • Not to me. It misses the words "very urgent" and "drop everything you're currently doing".
      • Along with the sinking feeling in your stomach which comes from the knowledge that working on the current #1 highly-visible problem won't excuse you from having to get all your other #1 priority work done on time.