Foreword
This article is a summary of an article by Zhang Xinxu. Original Link. Clicking is not recommended; proceed at your own risk.
1. Sending an Email
The choice of contact method is very important. Email is not instantaneous, but it is reliable. I recommend using email. In urgent cases, you can use email + SMS + phone call, though the latter two are just to notify them that you've sent an email.
Instant messaging tools are the worst choice, such as QQ or WeChat, because they are inefficient. Something that could be explained in one or two lines of text might waste 30 minutes on a chat tool.
2. Carefully Crafting Email Content
1. Do Not Start with Fluff
For example: "Are you there? Are you familiar with XXX technology?" or "Hello, can I ask you a question?"
A senior's time is valuable; they don't have time for fluff.
2. Pay Attention to Tone and Manner
For example, the "Big Boss" style:
Hello, XXX, I saw XXX you wrote online and don't quite understand some parts. Could you answer them for me? Please reply upon receipt. Thank you! Sincerely, XXX (My QQ: *******, I hope you can add me as a friend.)
At first glance, it seems reasonable and even somewhat respectful, but the tone is genuinely uncomfortable, isn't it?
3. Describe the Content Clearly
For example:
Hello, sorry to bother you. I've been doing such-and-such lately and discovered XX problem. Do you know what's going on?
Brother, I'm currently facing a very thorny issue: how can I do X with XX...
Even more common:
Hello! I saw this tool you made on XXX. I used it on XX, but it doesn't work. What's the deal? Thanks! [rar attachment]
This type of SMS-style description is very inappropriate for an email. We should describe the problem in a structured way, for example:
- Environment and Background of the Problem
Problems are often highly environment-dependent, so you must explain the background.
- Description of the Observed Problem (Screenshots)
You must clearly state what the problem is. It's best to provide screenshots; one look at a picture might instantly reveal the issue.
- Your Own Thought Process and Perspective
You shouldn't ask questions mindlessly; you should respect the senior's time. Furthermore, describing your thought process helps explain the problem more clearly.
- Necessary Key Source Code
Essential for programmers asking questions, but be careful not to make it too long. It's best to highlight the key parts and add comments, because seniors also suffer from "TL;DR."
- Online and Previewable Demos
The most efficient way. If the problem can be reproduced online, the senior can address it directly. Ideally, you send a link (the problem), and 10 minutes later, they reply with a link (the solution)—without any fluff.
4. Email Attachments
Avoid adding attachments as much as possible, as they require downloading -> extracting -> opening to be seen. Try to describe everything clearly in the body of the email; you can even add syntax highlighting to the code.
Use ZIP format for compression, not RAR, because macOS cannot open RAR files natively.
5. Explain the Problem Clearly in One Go
The advantage of email lies in the absence of small talk, chitchat, and other fluff. Strive to explain the problem simply and clearly in a single email so the recipient can understand the situation fully and provide a solution.
If you keep going back and forth with endless back-and-forth, the advantage of using email is completely lost.
3. Other Considerations
1. Timing
Is the other person busy? Are they at work? Will they be annoyed on a Monday? Will they be unavailable on a Friday?
People are naturally more inclined to reply thoughtfully when they're in a good mood, aren't they?
2. Subject Line
The subject line is crucial. Try to include as much information as possible so the recipient can grasp the situation without even opening the mail. This increases the importance of your email in their inbox and catches their attention.
3. Strive for Brevity
Again, because of "TL;DR." Would you read a 1,000-word narrative essay? I certainly wouldn't.
Avoid rambling emails that lack a clear point; the recipient might not even know how to respond.
Afterword
The reason for this article is primarily because the original was too verbose. Compared to the rambling Xin Space by ZXX, I prefer SF's Front-End Observation.
No comments yet. Be the first to share your thoughts.