/note/comms.html: Further update communication guidelines.

1 files changed, 9 insertions, 3 deletions

diff --git a/note/comms.html b/note/comms.html
index fc3bc6d..5055a86 100644
--- a/note/comms.html
+++ b/note/comms.html
@@ -14,10 +14,16 @@
 		</p>
 		<ol>
 			<li>
-			Write a descriptive subject for emails.  Do not send emails with an empty subject or no subject header.  Subjects help navigate emails.
+			Write a descriptive subject for emails.  Do not send emails with an empty subject or no subject header.  The subject should be give the receiver a brief idea of what the email is about.
 			</li>
 			<li>
-			Send complete information.  When telling me something or requesting something, please provide complete background information, knowledge required, and similar things.  As a general rule-of-thumb, the explanation should usually be longer than three sentences or a few paragraphs depending on the complexity of the task at hand.  This prevents back-and-forth communication along the lines of ``and now I need to know ... but you didn't tell me that so can you please give that to me'', generally defragmenting conversations which increases efficiency and comfort.
+			Send complete information.  When telling me something or requesting something, please provide complete background information, knowledge required, and other relevant context.  This prevents back-and-forth communication along the lines of ``and now I need to know ... but you didn't tell me that so can you please give that to me''.  Providing context defragments conversations which increases efficiency.
+			</li>
+			<li>
+			When using instant messaging such as IRC, do not split one sentence into multiple messages.  Fragmentation reduces readability.
+			</li>
+			<li>
+			Do not use excessive emojis.
 			</li>
 			<li>
 			Be direct.  As the sender, do not use polite expressions like ``you did quite well in that presentation'' when in reality, the sender believes that the presentation is not ``quite well''.  Direct critique and suggestions are very welcome here&mdash;politeness is acceptable if it does not interfere with honest conveying of information.
@@ -26,7 +32,7 @@
 			<a href="./ask.html">Don't ask to ask.</a>
 			</li>
 			<li>
-			Use plain text email.  Both hard-wrapped and non-hard-wrapped emails are acceptable.
+			Use plain text email.  Both hard-wrapped and non-hard-wrapped emails are acceptable.  If you do hard-wrap, please wrap at 72 characters for English.  Do not hard-wrap Chinese.
 			</li>
 			<li>
 			Interweave the original message with the response when replying to an email and remove irrelevant parts (i.e. greetings, closings, signatures, etc.) of the quoted original email.