On Wed, Nov 18, 2009 at 3:30 PM, Michael Torrie <[email protected]> wrote:
> As as aside, whenever I get a top-posted reply to something I've said, > it immediately tells me that the person didn't read anything I wrote and > is just running his mouth. This is especially annoying when > corresponding with professional management types or tech support people > via e-mail. Try it as an experiment sometime. E-mail your boss and ask > three distinct questions. If he e-mails you back a top-posted reply, > odds are he only ever saw one question. Pretty sad how unprofessional a > lot of management types are. > > So a word to the wise. When corresponding professionally, always trim > and always post replies in-context. This tells people (like your boss) > that you're conscientious and that you always read everything and > understand it _before_ you reply or react to it. The parts you are not > quoting are the parts you are unable or unwilling to reply to. If you > don't have a need to post in-context, trim the entire email. This is > just a UUG list, but each of us will have a real job some day, and > effective communication is important. May as well start here. > > As for long, off-topic threads, well you all *do* use procmail, right? > Or if you have to use gmail, filters? > > I've been thinking lately that if the Google Wave idea catches on, how it will affect top/bottom posting, thread hijacking, etc. It's kind of a clever idea, but it doesn't work with standard e-mail currently which is going to kill adoption. Although it still a year off from a real Google beta, I'm watching it closely as I'm interested to see how something so drastically different will be adopted. I don't have to remind you of what happened with Vista, can Google learn from Microsoft's mistakes? I'm not jumping on any bandwagons, but I'm going to enjoy being a spectator. Robert LeBlanc Life Sciences & Undergraduate Education Computer Support Brigham Young University
-------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list
