写作方法2012randsinrepose.com编辑精选
请学会写作
Please learn to write
导读
这则 HN 讨论围绕“请学会写作”展开：很多工作低效并非技术问题，而是别人看不懂、说不清，写作能力因此直接影响协作效率。对写作者来说，它提醒我们把写作当成日常沟通工具，并通过持续练习、明确读者和找人审读来提升。
可以直接用的写作要点
- 01
把写作当成沟通工具，先问读者能否一次看懂，再追求文采。
- 02
用固定节奏写作，比如每周更新，比“有空再写”更容易持续进步。
- 03
写完交给他人审读，重点检查哪里让人困惑、有无错别字和未完成的句子。
- 04
根据读者调整语气，可用对话式表达、少量幽默和比喻，但要避免术语和过度随意。
HN 评论精选
工作低效主要来自沟通，尤其是写作不清；多写是解药。
我工作中问题的来源大致是：设计问题5%、架构约束5%、语言缺陷1%、心理障碍5%、个人时间管理4%、精力5%，而与他人的沟通占75%。我大量时间浪费在搞清别人想说什么，主要是书面表达。大多数邮件我得点“回复”或打电话，只因对方说得太不清楚；上次收到能直接照着做的书面规格还是2002年。这不是教育、国籍或人群问题：几乎所有人都写得很差，这是真问题。改善写作最好的解药是更多写作，尤其是在线写作；别害羞，读者不会客气。
edw519查看英文原文
Source of my problems: design issues 5% architecture constraints 5% language shortcomings 1% mental blocks 5% personal time management 4% personal energy 5% communication with others 75% I waste more time just trying to figure out what others are trying to say, sometimes in person and by voice, but mostly in writing. For most emails, I have to click "reply" or call back simply because what you're trying to tell me is so unclear. I think the last time I received a written specification I could actually work from was in 2002. This isn't a problem of education, country of origin, or any other demographic: almost everyone sucks at writing. It's a real problem. I suppose the best antidote to poor writing is more writing, especially on-line. Don't be bashful because as OP says, your readers won't be. Thanks OP for the one "please" post this week that everyone can benefit from. (Did I just end that sentence with a preposition? Need more practice.)
固定节奏、明确读者、合适语气和编辑审读能让写作更有效。
我是程序员，开始给应用用户写每周简报，格式是“本周发生了什么”“下周可能发生什么”，以及“有想法请联系我们”。14周后我有几点体会：向用户解释工作能让你聚焦可演示的进展，而不是过度打磨；提高写作的方法就是写；人们偏好渐进变化，尤其提前告知时；人们在意写作质量，有人竟说喜欢读简报；语气重要，对话式加一点幽默自嘲但别太随意，面对非技术用户不能漏术语，比喻有帮助；节奏重要，每周更新比“随时写”容易；有编辑有帮助，我写完整消息后交给同事发出前检查是否让人困惑、有无错别字或未完成句子。
MartinCron查看英文原文
I'm (primarily) a coder and I've started writing a short weekly newsletter for the users of the application I'm supporting and extending. The basic format is "what happened this week" and "what may happen next week" as well as a "please communicate with us if you have concerns or ideas". I'm now 14 weeks into this experiment, and I've found a things worth sharing. 1. Explaining to your entire user base what you're up to helps you focus your efforts on meaningful demonstrable progress instead of gold-plating. 2. It has been said a hundred times before, but the way to get better at writing is to write. 3. People prefer incremental changes over disruptive redesigns, especially if they are given a heads-up before the incremental changes happen. 4. People care about the quality of writing. I've gotten a bunch of comments about how they actually enjoy reading the newsletter. That was totally unexpected. 5. Tone matters. I've found a good conversational tone that incorporates just a touch of humor and self-deprecation without being too casual. My userbase is non-technical, so I can't leak jargon on them. Metaphors help. 6. Cadence matters. Writing a weekly update is much easier than writing an update "just whenever". 7. Having an editor helps. I generally write the entire message, but pass it along to comrade to send it out to see if anything is confusing, I've made any typos, or forgot to finish one of my sentenc
沟通能力比精通某编程语言更能推动职业发展。
我大学计算机顾问给过我最好的职业建议。我问学C、Java等能否比别的程序员更强，他说去学能提升沟通的东西。现实中商业常把你看作“计算机的人”，分不清程序员、网络工程师和PC支持。任何人都会写代码，真正的高手未必被管理层认可；计算机人常被视为内向，能说好并和所有人沟通，比精通某门语言走得更远。
jkeel查看英文原文
One of the best pieces of advice I received for my career was from my university's computer science counselor. I asked him what I needed to do/study to be better than other programmers. I started asking, "should I study C, Java (it had just come out), etc. He said study something to improve your communication. He said in the real world business just look at you as a computer person. They don't know the difference between a programmer, network engineer, PC support person, etc. He said anyone can code and the ones that are way better will not be recognized enough by management to make a difference in their careers. Since computer people are sort of known as introverts, just being able to speak well and communicate with everyone will go further than being the expert at language X.
沟通不清会让思考价值被低估，甚至被绕开。
沟通技能是批判性思维的代理指标：如果你不能有效沟通，你的批判性思维就会被低估或未被充分利用。理解不足会让沟通输入被误解、忽略或错误回应；清晰、精确、可理解不足会让输出遭遇同样命运。就像网络中的低效环节会被绕开，那个邮件让人莫名其妙的工程师也会被绕开。
VengefulCynic查看英文原文
Communication skill is a proxy for critical thinking skill - if you can't communicate effectively, your critical thinking skill is either going to be undervalued or underutilized. For the lack of understanding, communication inputs are misinterpreted, ignored or incorrectly responded to. For the lack of clarity, precision and understandability, communication outputs suffer the same fate. And, as we've learned in networking, inefficiencies in a system (such as the engineer whose emails make no sense, when he/she bothers to reply at all) get routed around.
同类还值得读
被低估的工程技能：把文章写好
Undervalued Engineering Skills: Writing Well
这篇文章讨论为什么“写得好”是被低估的工程能力，以及它如何在团队协作、系统设计和职业发展中持续带来回报。
写作方法2019 · 1,109 分 · 371 评4 条写作要点编辑精选每行只写一句话：让写作和修改都更轻松的排版法
Writing one sentence per line
这是 Derek Sivers 的一篇短文，主张写作时每行只放一个句子，而不是按段落排版。
写作方法2022 · 849 分 · 297 评4 条写作要点编辑精选书面沟通是远程工作的超级能力
Written communication is remote work super power
这篇文章讨论远程工作中书面沟通的价值，评论区则补充了异步与同步沟通的适用场景，并提醒读者：备忘录、结论先行、结构化命令格式等书面沟通传统早已有之。
写作方法2020 · 831 分 · 190 评4 条写作要点编辑精选如何写出有用的文字
How to Write Usefully
保罗·格雷厄姆在这篇文章里给"有用的写作"下了一个可操作的公式：有用≈重要×新颖×正确×清楚，任一项为零，整篇文章就等于零；他还主张敢下确定判断、删掉让自己心虚的句子。
写作方法2020 · 821 分 · 285 评4 条写作要点编辑精选如何写得更清楚、想得更清楚，并学会复杂材料（PDF）
How to write more clearly, think more clearly, and learn complex material [pdf]
这份 PDF 讨论如何把文章写清楚、把思路理清楚，并用写作来学习复杂材料。
写作方法2022 · 779 分 · 153 评4 条写作要点编辑精选