While some devs probably find this an acceptable, even humourous attitude, end-users who are stuggling to explain a bug they've run into may feel infuriated if that's your response.
I know as well as you do that fixing a bug that can't be reproduced is near on impossible sometimes.
For those not familiar with testing in general, if you can't reproduce a bug, how can you:
(a) identify the bug ?
(b) fix it ?
and
(c) prove that you've fixed it?
Internally, its fine to joke around and say "it never happened" but all reports for this "phantom" bug need to appended onto the original bug report. If the bug truely exists, eventually, you'll have enough dots to draw a line between them and identify the bug...
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.