As you might guess, I get a lot of email from readers of Macworld and macosxhints.com. For the most part, I love hearing from readers -- even if it's negative feedback, believe it or not. In the case of negative feedback, however, it's nice if the writer provides enough detail so I know (a) what they're upset about, and (b) what I might be able to do about it. I've actually had many useful and productive exchanges with folks who wrote to flame me for one reason or another.
However, on the opposite side of the fence, as an example of the kind of useless feedback I hate receiving, I offer up this email that arrived this morning:
Do you proof read these articles before you publish them?
That was the entire email. I have no idea which typos the author may be referring to, nor for that matter, which one of the 20 to 30 things I wrote last week that those typos may be in. It's also somewhat ironic to note that proofread is one word, not two -- if you're going to chastise me for typos, it's best not to make any of your own!
I really do enjoy hearing from and corresponding with readers. But if you're going to take the time and effort to write to me, at least include enough information for me to understand what it is that's gotten your attention, so that I have some context for your comments and can respond in a meaningful manner.