写作方法2013ninjasandrobots.com
Draft：为写作而生的版本控制
Draft. Version control for writing
导读
这篇介绍了一款面向写作者的版本控制工具 Draft，把 Git 式的修订管理引入文档写作。对写作者的价值在于：它提醒我们，真正需要版本控制的往往是最复杂的长文档（年报、长篇作品、论文、合同），而修订界面如何呈现差异，直接决定协作审阅的效率。
可以直接用的写作要点
- 01
越是复杂的长文档（长篇、论文、合同）越需要版本控制，别只靠文件名区分「终稿」「终稿2」。
- 02
差异对比要落到词一级：让审阅者能一眼看出「Sharing→Saving」这类改动并直接接受或拒绝，而不是自己去猜上下文。
- 03
把「大版本存档」和「自动保存」分开管理，既保留关键节点，又不怕丢失过程稿。
- 04
给非技术合作者用的修订工具，必须比 Git 和 Word 修订模式更简单直观，否则协作方不会用。
HN 评论精选
最需要版本控制的是复杂长文档，而纯网页应用可能覆盖不了这类离线重负载场景。
看起来很酷，但我第一反应是：最需要版本控制的恰恰是最复杂的文档——年报、长篇作品，那些需要复杂文档元素、让 Word 显得臃肿的东西（而且这些文档还得能离线编辑）。把这项服务做成网页应用，似乎会让这些场景无法实现。
jmduke查看英文原文
This looks cool, but my immediate thought was that the documents most in need of version control (and Word offers version control, but its hardly as elegant as what this purports) are the most complex ones: annual reports, long-form works, things that require the complex document elements that make Word feel so bloated sometimes. (Not to mention that these are documents that need to be worked on offline.) Branding this service as a webapp seems like it's going to make those use cases impossible.
差异界面应按词展示完整改动，让审阅者能立刻判断接受或拒绝，而不是让他自己猜。
不错，原理上类似许多报纸生产系统（Quark Publishing System、Atex 等）的做法：把重要修订版本和自动保存分开存放。一点意见：差异对比界面太「程序员化」了。「har」对「av」光看根本没法接受或拒绝，你得自己解析上下文猜出原词；而「Sharing」对「Saving」、「Insanley」对「Insanely」这种就能立刻判断是或否。
bonaldi查看英文原文
Looks good. Similar in principle to how a lot of newspaper production systems (Quark Publishing System/Quark CopyDesk, Atex etc) work - store major revisions alongside autosaves. One comment: the diff screen is a bit too programmery. "har" vs "av" is impossible to accept/reject just from looking at it - you have to parse the context and work out what the words are. "Sharing" vs "Saving" or "Insanley" vs "Insanely" is much easier to immediately yes/no.
细粒度的改动审阅加上审批流程，是多人合作写论文的核心需求。
好主意。Word 式的修订功能远不如 Git 简单强大（前提是你已经搞懂了 Git，而这对很多非程序员并不现实）。我很希望有这种东西，用来和非技术背景的作者合作学术论文：论文（其实任何技术文档）里能看到细粒度的改动非常重要，尤其当研究生或研究助理做的修改需要由项目负责人审批时。Google Docs 勉强能做，但不支持任何文献引用管理。如果它真的好用并能配合文献管理，学者们会很喜欢。（我个人觉得学术界是最需要它的地方。）
masnick查看英文原文
This is a great idea. Microsoft Word-style version control (track changes) is not nearly as simple and powerful as Git (assuming you have already wrapped your head around Git, which isn't a reasonable expectation for many non-programmers). I would love to have something like this for collaborating with non-technical authors on academic papers. Having a granular view of changes in an academic paper (or really any technical document) is really important, especially if you have grad students or research assistants making changes that need to be approved by the principle investigator. Google Docs sort of does this, but it doesn't support any kind of citation management. (All citation management possibly excepting Papers2 sucks; BibTex seems too technical; but this is a whole other thing.) But this looks way better than version control in Google Docs. If it really is easy to use and it works with some system for citation/bibliography management, I think academics would love it. (Academia is the place where I personally see the greatest need for this. I don't mean to ignore or detract from other use cases that may be more prevalent.)
合同与法律文书的团队协作是版本控制的刚需场景，值得做成垂直市场。
有没有考虑做行业垂直市场？版本控制在法律行业——或者说任何需要团队协作起草合同的行业——是巨大得不能再巨大的痛点。走企业路线，把产品卖给大律所，或者授权给学校，应该能赚不少。
jonnathanson查看英文原文
Have you considered an industry vertical? Version control is a huge-beyond-huge annoyance in the legal profession, or frankly, in any profession involving group work on contracts. I imagine you could make a decent chunk of change going the enterprise route and selling this to big firms, or licensing it to schools, or what have you.
同类还值得读
被低估的工程技能：把文章写好
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 条写作要点编辑精选