i am dustin diaz

Seven Things not to report in a bug

Over the years I've been handed quite a number of bugs to track, fix, contemplate, investigate, eradicate, duplicate, compensate, and ignore. This has all come about through either past clients, co-workers, or direct overseers. With that said, here are seven things in all good fun that I don't need to hear.

Seven things you shouldn't say when reporting a bug to a developer

1. This font is ugly: I'm sorry, let me change the css from font-style:ugly; to font-style:pretty;. If it's noted in some specification on a requirements list, then by all means, just tell me that instead. For something that can be subjective, who's one to say what's ugly or pretty. One man's verdana is another man's georgia.
2. This page is messed up: Really? Enlighten me.
3. I don't understand how to use this: Great. Thousands of dollars lost on all those test cases. What were we thinking?
4. Awkward Interaction: Does it work? Is it broken? Are you clicking anything? Is it awkward to just you?
5. Please add 'such and such' to the code: Thank you very much. Would you like to fix the rest of the bugs?
6. This runs slow on my machine: Did you test this anywhere else? Wait, aren't you the one who continually uses Mac OS8? I can remember countless of times I'd receive a bug because someone would be doing some testing at home on a computer that is 0.001% of our user base.
7. The text is wrong: A Developers nightmare of receiving a content bug. Generally, developers aren't responsible for what a document says. Granted if it's a typo, then yea... it could be our fault, but I've received this bug enough that it was just plain out not my fault.

What's your seven?