博客与个人写作2011swombat.com编辑精选
博客写作的问题
The problem with blogging
导读
本文讨论博客这种载体本身的结构性问题：按时间倒序排列、追逐“当下”的博客模型，会让不依赖时效的内容（思想随笔、经验总结、技术洞见）迅速沉底，价值被浪费。作者提醒写作者：先想清楚自己写的是“日记式时事评论”还是“可长期沉淀的常青内容”，后者不该被塞进时间线里。
可以直接用的写作要点
- 01
先判断自己写的是时效性内容还是常青内容；如果是后者，就不要把它塞进按时间倒序的博客结构里，按主题分类整理成“文章”或“专栏”。
- 02
不要指望最新一篇比旧文更重要：常青内容的价值不随时间衰减，甚至旧文可能更值得反复阅读和引用，写作时应按长期价值打磨。
- 03
把零散博文当作一本书的章节来规划：先列目录、再填补内容，允许它暂时不完整，然后持续积累，比零散发布更利于沉淀价值。
- 04
警惕评论区稀释作品：开放评论会让读者把你的文章当成对话素材而不是完整观点，重要的、成熟的思考应放在能体现其分量的地方发表。
HN 评论精选
博客混用了“日志”和“常青写作”两种用途，后者不适合按时间排序的模型。
博客其实混用了两种截然不同的用途。第一种是把博客当日志，记录当下的事件与评论，比如私人生活、职业见闻、新闻；这类旧内容确实会快速失去相关性，因为事件本身已经过去了。第二种是写不依附于当下时刻的内容，比如哲学思考、有趣的数据结构、人生建议、Paul Graham 式的文章；这时博客模型就不合适了，新文章并不比旧文章更重要，甚至可能更不重要。他还提到“偶然发现”的问题：作者写过其他你可能会喜欢的内容，即便主题不完全相同；这可以用协同过滤之类的方法解决，再配合不按时间排序的 CMS 式知识架构，才可能找到出路。
kylemaxwell查看英文原文
So there are at least two separate use cases that get shoved into blogging. The first (and probably most useful) treats the blog as something like a diary: commentary on current events at some scale, e.g. personal, professional, news, et cetera. In this case, older content really does have much less relevance because the events themselves now live in the past. Your friends /might/ care about what you drank last night, but they almost certainly don't care about 5 months 12 days ago. You might want to comment on Linus' latest mailing list screed, but it might not matter for kernel-dabbling four years down the road. The second use case seems to be where Daniel Tenner really is chewing on something. If you're writing new stuff that doesn't necessarily live in the moment - musings on philosophy or cool data structures or life advice or Paul Graham's articles - then the blog model doesn't fit as well. Newer posts don't matter more than older posts, and in fact might matter less. Thinking on this, we also have the issue of serendipity. The writer has probably created other stuff that you might like reading even if it's not directly about the exact same topic. Seems like the sort of thing attacked by collaborative filtering and other methods. Combine that with a CMS-style knowledge architecture (e.g. structure by something other than chronology if chronology doesn't make sense), and you're getting somewhere.
开放评论把文章降格为“对话素材”，成熟的想法应换一种更能体现价值的发表形式。
博客这种形式还会贬低内容价值：同样的观点和文字放在别的场合会更有价值，但博客把它们呈现为天然“未完成”的东西。比如开放评论会诱导读者不把你的文章看作完整成熟的想法，而只当作聊天的素材；如果你本来就想讨论，这很好，但如果你的作品因此被评论区里最水的那部分声音评判，就很糟糕。Daring Fireball 能成立是因为那是他的本职工作，站点本身就是精心分析的新闻简报。但如果你是一家有产品的软件公司，只是顺带产生了关于软件、技术、产品的好想法，及时新闻简报并不是你的本职；要发布就该以最大化这些想法价值的方式发布。他自己的想法是把博文重新整理改写成书：先列目录，用旧文填空，允许它不完整，逐步完善。
tptacek查看英文原文
This is something Patrick McKenzie has been saying here for almost a year now, and is part of the reason we stopped blogging despite having developed an audience. Another thing that devalues blog content, where the same ideas and prose would be more valuable in another venue, is that they present pieces as inherently incomplete. Example: blog commenting, which encourage readers to see pieces not as fully developed ideas but simply as fodder for a conversation. That's great when a conversation is really what you wanted, but it's terrible when it results in your work being scored by the lowest common denominator of your comments. Daring Fireball works because that's his job. It is the point of the site to be a carefully analyzed news bulletin. But when you're (say) a software company with a product and, possibly as a result of that product, some interesting ideas about software, technology, products or what-have-you, a timely news bulletin is not your job, and if you're going to publish, you should do it in a way that optimizes the value of those ideas. For our part, I'd like to reorganize and rewrite our blog posts into a book; start with a TOC, fill in the blanks with posts, let it be incomplete, and build it up over time. But I'd also like to get product shipped.
聚合器只奖励“此刻”，无固定读者的博主的旧文很难被看见，需要能自主分发的新模式。
完全同意，而且这不只是单个博客的问题，而是整个网络内容生态的问题。过去几年 RSS 订阅数大幅下降，被 Twitter、Facebook、HN、Techmeme 等取代；这些站点都强调“此刻”，12 小时前的故事就算旧闻。一个话题可以在短得连主要时区都没轮完的时间里浮现又消失（在澳洲他常错过大事，因为那些内容只在美国时间的几小时里挂在首页）。所以需要适应的不只是个人博客模式，还有聚合器和客户端的工作方式：大家都盯着过去几小时发生了什么。几年前他在 Techcrunch 写过“随时间的相关性”，讨论博客、Twitter 该如何适应；这些方案似乎都没奏效。结论是：如果你是没有固定读者群的博主，就只有偶然被大型聚合站推上去的那几篇能获得像样的阅读量。他认为新的分布式社交网络会成为新的博客模式，可以发布和订阅，不必依赖面向大众的聚合器来分发内容。
nikcub查看英文原文
Interesting post - completely agree with it. It isn't just with individual blogs, it is with all blogs and content on the web. The number of RSS subscribers has drastically decreased in the past few years - and it has been replaced by Twitter, Facebook, HN, Techmeme et al. Each of these sites emphasizes the now - to the extent that a 12 hour old story is old news. An entire story thread can surface and then disappear in a span of time that doesn't even last through the major global timezones (in Australia I often miss big stories because they are only up top for a matter of hours on US time) So it isn't just the individual blogging model that needs to adapt, it is also the way aggregators and clients work. Everybody seems to be stuck focusing on what has happen in the past few hours. A few years ago I wrote on Techcrunch about 'relevance over time'[1] and how the blogs, twitter etc. need to adapt. None of the solutions have seemed to work, and all that means is that if you are a blogger and do not have a regular audience that checks your blog regularly, you are only going to get a decent number of readers for the odd post that surfaces its way up onto one of the large aggregators I think that the new distributed social network will become the new blogging model - where you can pub and sub and not rely on aggregators that are tailored for a mass audience to find content. I am disappointed that all the new 'facebook alternative' projects are just about replacing or complementing facebook, rather than re-thinking the entire space of personal publishing. I miss the old blogosphere and would like to see it reborn in some way. Edit: and as an example, I to manually tweet this comment. It doesn't appear on my blog, you can't reply to it from your own blog, and within 6 hours it will be long forgotten and we will have the same conversation again in 3 months time. [1] http://techcrunch.com/2009/10/12/relevance-over-time/ and followup: [2] http://nikcub.appspot.com/relevance-time-for-twitter
解决办法很简单：不按时间排列，按主题分类呈现。
那就别再按时间顺序对待你的文章了，把它们叫作“文章”，并按类别来组织。
saraid216查看英文原文
Stop treating your posts chronologically, then. Call them essays and make a categorical listing.
同类还值得读
我坚持每天写一条 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 条写作要点编辑精选