博客与个人写作2018200wordsaday.com编辑精选
公开写一本书
Writing a book in public
导读
这篇讲作者公开写作一本每天200词的书，评论补充了实际写作与编辑经验：先动笔、别过度定义、手稿需专业编辑、日更可练习。值得写作者读，因为它把“持续写”与“成书流程”拆开，提醒避免准备陷阱。
可以直接用的写作要点
- 01
先写正文，不要用搭工具、建术语表或做准备工作替代写作。
- 02
把初稿和成书分开：写完只是开始，需专业编辑反复打磨。
- 03
设定低门槛日更（如200词），用公开记录维持节奏；但排期要计入编辑耗时，100个可读词可能需要500到1000词草稿。
- 04
接受知识传播的“果酱定律”：书面表达会变薄，重要反馈和互动要另找渠道。
HN 评论精选
写作要少做准备工作，先动笔；成书需编辑，且书面传播有天然损耗。
我写了一本书——更准确地说，是把同一本书写了四遍：写、学、丢弃、再写、迭代、编辑、重排、丢弃、重开……心得：一，只管写；我第一版搭了极花哨的写作环境，结果浪费时间没写书。二，别“维特根斯坦式”地死抠定义，先定义网站、域名等术语是作者的“削牍”式拖延，别做，只管写。三，手稿不等于书；写完后真正的工作才开始，手稿的阅读感、流畅度不同于书，要找专业编辑合作，不合适就换，合适编辑对书成功很重要。四，接受“果酱定律”：知识铺得越开越薄；一对一或工作坊能比书传递更多知识，因为互动有直接反馈。
franze查看英文原文
I wrote a book[1] - well - i wrote the same book 4 times again and again, writing, learning, throwing away, writing, iterrating, editing, rearranging, throwing away, starting new, iterrating, ... . Some learnings: I) just write first attemp i made a super fancy setup - google chrome book with custom linux installed that automatically transformed markdown via pandoc into a custom styled PDF everytime i saved. was fun to create this setup, but i wasted time not writting the actual book. II) don't wittgenstein i wanted to be absolutely correct, so i started with defining word, what do i mean with website, domain, webproperty, webpage, page, link, external duplicate content, internal duplicate content, ... or any other technical term. wittgensteining is yak shaving for authors. don't do it. just write. III) a manuscript is not a book after you are finished, the real work start. a manuscript does not have the same feeling, read-feeling, read flow as a real book. get a professional editor, work with him/her. fire him/her if not the right match, find the right match, start again. the right editor is as much a factor for the success of the book as the author. IV) live with the law of strawberry jam the further you spread knowledge/jam the thinner it gets. yes, in a 1:1 talk, in a 1:12 people workshop you can communicate more knowledge than you can with a book. talk, interaction, any form of communication with exchange, has direct feedback - something unbelievable important for information communication. a book is a one way street with - if at all - delayed feedback. you can always continue writting, pack in more knowledge, more details, more clarificaiton, more scenarios, but then the book will never finish. at one point you have to stop. V) cut away go through your book again, and question every word, every sentence, every paragraph, every chapter. if the word, the sentence doesn't ad substential value, get rid of it. your book will be better. it's not about quantitiy of words, it's about what you want to say. VI) let go & publish, just do it. [1] "Understanding SEO - A Systematic Approach to Search Engine Optimization" https://www.fullstackoptimization.com/b/understanding-seo ISBN: 978-3-200-05426-4
与NaNoWriMo类似，明确日更目标降低门槛，但时限有助于专注。
这很像 NaNoWriMo（最初指“全国小说写作月”）：11月挑战写5万字小说，有字数追踪和社区互动。区别是这里更明确每天200词（NaNoWriMo隐含日均远高于此），且不受时间限制；不过NaNoWriMo的时限确实有助于集中注意力，尽管维持其目标很难，200词/天相比之下很轻松。
Xophmeister查看英文原文
This is very similar to NaNoWriMo[1], which originally stood for "National Novel Writing Month" (I say "originally" because the "National" bit no longer applies), whereby you sign up to try to write 50,000 words of a novel in November. It has similar word tracking features and a community of other users whom you can interact with (IIRC; the last time I signed up was 2012). The only real difference is that the words/day is more explicit here (200 vs. an implied average of over 8x that) and that you're not constrained by time. While it is pretty hard to maintain the level required to achieve the goal set by NaNoWriMo -- 200 words/day is trivial, in comparison -- the time constraint certainly helped focus. [1] https://nanowrimo.org/
日更目标要计入编辑成本，实际产出比草稿字数少很多。
得把编辑算进去。按合理说法，我曾看到一页讨论：要得到100个可读的词，可能需要写500到1000词，所以所需时间是5到10倍。另一方面，每天200词很低，真正进入状态后很容易到500到1000词/天。
distant_hat查看英文原文
You'd have to take editing into account. By any reasonable account, I saw a page that discussed it once, to have 100 readable words, you'd need to write 500-1000 words. Which means the time required goes to 5-10x. On the other hand, 200 words per day is pretty low, you could easily get up to 500-1000 words per day once you really get going.
每天200词可通过日常评论练习，公开写作不是唯一途径。
这是全职工作，但并没妨碍我连续一个多月每天至少写200词。作者可能会惊讶，很多人早已通过论坛评论这样做。我多年把用英语写评论当作日常练习。
Tade0查看英文原文
This is a full-time job, but it did not prevent me from writing at least 200 words daily for over a month now. The author would be surprised to note that many people do that already via forum comments. I practice my english this way and made it a part of my daily routine years ago.
同类还值得读
我坚持每天写一条 TIL，已经写了一年
Show HN: I've been writing daily TILs for a year
这篇展示作者一年每天写 TIL（Today I Learned）并整理到 GitHub 仓库的做法。
博客与个人写作2016 · 819 分 · 150 评4 条写作要点编辑精选如何写出开发者愿意读的博客文章
How to write blog posts that developers read
这篇（正文与评论未提供，仅从标题判断）讨论面向开发者写技术博客的方法：怎样让忙碌的工程读者愿意点开、读下去并读到结尾。
博客与个人写作2025 · 603 分 · 154 评4 条写作要点编辑精选博客写作风格指南
A blogging style guide
这是程序员兼博主 Robert Heaton 的博客写作风格指南，用几十条简短规则讲如何让技术文章更清晰、更好读。
博客与个人写作2018 · 495 分 · 188 评4 条写作要点编辑精选十年职业博客写作，我学到了什么
Ten years of professional blogging – what I’ve learned
这是作者回顾十年专业博客写作经验的总结，评论补充了写作作为深度学习、聚焦主题、保护写作习惯和选择发布平台等实践。
博客与个人写作2017 · 362 分 · 126 评4 条写作要点编辑精选十年博客写作教给我的事
What I learned in ten years of blogging
这是一篇博客作者十年写作经验总结，核心观点是写作的价值在于持续积累而非单篇爆款。
博客与个人写作2018 · 356 分 · 162 评4 条写作要点编辑精选