False analogy. 7 billion hairless apes on the horizon show that bug is trivial to reproduce.
I agree it's important to be sensitive to users and their inability to describe problems well and the possible shortcomings in documentation and UI that exacerbate the situation but when you hit a bug that is impossible to reproduce the chances it was PEBKAC are 1,000 times greater than it being some mystery that must be solved and justifies chasing for a few hours or a few days.
If it's really not reproducible given a good try, split the difference. Drop some new test and logging around the reported area if it makes sense to try and tell the user you're investigating further. (This advice is not pertinent to banking and medical applications where bugs could possibly mean prison time or dead patients.)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
