n0ov
05-18-2004, 05:42 PM
Here's a document circulating at work that I thought would be fun to post on QRZ just for the reaction. #Kind of hits close to home # http://www.qrz.com/iB_html/non-cgi/emoticons/biggrin.gif
</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote </td></tr><tr><td id="QUOTE">E-Mail Etiquete
1. #Shouting: #Do not shout. #Shouting is using all caps, using a large font or even using an abrasive color such as all read. #Another example of shouting may include too much punctuation.
2. #War and Peace Syndrome. #Be brief and plan your message. #Analyze your reader's needs to be certain you're sending a message that will be clear, concise, and useful. #Long e-mail messages are difficult to read and frankly probably won't be read, so keep it brief.
3. #Be Fact-Based and Unemotional. #Emotions are hard to convey in emails and can be easily misinterpreted. #Be careful when using humor or sarcasm in messages. #Re-read your messages or ask someone else to read it to see if it could be misinterpreted.
4. #Use smilies and emotions sparingly. #There are hundereds of these and their translations are not necessarily universal. #Misinterpretation can lead to confusion.
5. #Anger: #Emails are permanent records and angry emails often do more harm than good. #Everyone cools off over time, but an email does not. #For personal or problematic issues, it's best to discuss them one-on-one. # #If an e-mail must be sent, best to draft it and wait until the next day before sending it.
6. #Be positive: #Studies have shown that comments within emails take on a less positive tone than face-to-face discussions. #So try to keep your emails on the lighter side. #Remember, emails never die until deleted, so make sure that your message is one that can stick around for a long time without any ill effects
[/QUOTE]<span id='postcolor'>
There are several more, but I don't want to violate rule 2.
Wonder how this logic would apply to the posts on QRZ?
Hey CW & Packet Types: #Any similar rules for code or data?
</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote </td></tr><tr><td id="QUOTE">E-Mail Etiquete
1. #Shouting: #Do not shout. #Shouting is using all caps, using a large font or even using an abrasive color such as all read. #Another example of shouting may include too much punctuation.
2. #War and Peace Syndrome. #Be brief and plan your message. #Analyze your reader's needs to be certain you're sending a message that will be clear, concise, and useful. #Long e-mail messages are difficult to read and frankly probably won't be read, so keep it brief.
3. #Be Fact-Based and Unemotional. #Emotions are hard to convey in emails and can be easily misinterpreted. #Be careful when using humor or sarcasm in messages. #Re-read your messages or ask someone else to read it to see if it could be misinterpreted.
4. #Use smilies and emotions sparingly. #There are hundereds of these and their translations are not necessarily universal. #Misinterpretation can lead to confusion.
5. #Anger: #Emails are permanent records and angry emails often do more harm than good. #Everyone cools off over time, but an email does not. #For personal or problematic issues, it's best to discuss them one-on-one. # #If an e-mail must be sent, best to draft it and wait until the next day before sending it.
6. #Be positive: #Studies have shown that comments within emails take on a less positive tone than face-to-face discussions. #So try to keep your emails on the lighter side. #Remember, emails never die until deleted, so make sure that your message is one that can stick around for a long time without any ill effects
[/QUOTE]<span id='postcolor'>
There are several more, but I don't want to violate rule 2.
Wonder how this logic would apply to the posts on QRZ?
Hey CW & Packet Types: #Any similar rules for code or data?