Reporting bugs, making suggestions

If you developed tRev, looked in your email in-box and saw this subject line, what you think?

I don't get that many bug reports, I'm happy to say, but about 40% of them are sensational and downright un-helpful. Like this one.

In this case, tRev did not stop working. But how was I to know? I had to read the entire email to discover that one feature in tRev did not perform as expected.

I respond quickly to all reports, so there is absolutely no need to sensationalize a bug report to get my attention.

You should CLICK HERE to report a bug.

Say what the problem actually is—not how badly you feel about it. tRev doesn't do something you want it to do, so the whole program doesn't work? No. Say what it is that isn't working and tell me how I can replicate the problem.

If I can replicate it, I can fix it. If there is a work-around, I will advise you of it while I fix the problem.

Sometimes I get tRev not working subject lines, and it's a request for a new feature. When you want a feature, Tell me what—in a larger sense—you're trying to do. From requests like that, our best, new features have come.

If you're frustrated or unhappy, take a deep breath. Chillax. I'm not trying to make your life miserable. Because I'm enthusiastic about my product doesn't mean I'm indifferent to bugs or suggestions. Please don't assume a bunch of stuff, and then write tRev doesn't work.

That doesn't work for me. And therefore, it won't work for you.