summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorAndrew <andrew@andrewyu.org>2022-10-06 23:06:23 +0800
committerAutomatic Merge <andrew+automerge@andrewyu.org>2023-07-15 00:29:29 +0800
commit1329125ff146390b132851789a60ef3c415bb74b (patch)
tree8aa2058020458fa6b1c62650ef59617456a62035
parente6a599b92355b873190206121d1108285030e1ae (diff)
downloadwww-1329125ff146390b132851789a60ef3c415bb74b.tar.gz
/note/comms.html: Emphasize email subjects.
-rw-r--r--.DS_Storebin6148 -> 0 bytes
-rw-r--r--note/comms.html3
2 files changed, 3 insertions, 0 deletions
diff --git a/.DS_Store b/.DS_Store
deleted file mode 100644
index 42817fd..0000000
--- a/.DS_Store
+++ /dev/null
Binary files differdiff --git a/note/comms.html b/note/comms.html
index 952e5ad..fc3bc6d 100644
--- a/note/comms.html
+++ b/note/comms.html
@@ -14,6 +14,9 @@
 		</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.
+			</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.
 			</li>
 			<li>