博客与个人写作2014sites.google.com编辑精选
你应该写博客（2005）
You Should Write Blogs (2005)
导读
这是 Steve Yegge 2005 年那篇劝工程师都来写博客的经典文章，评论区从亲身经历出发讨论了写博客的实际收益与心理门槛。对写作者来说，它回答了三个具体问题：公开写作能带来什么、没东西可写时怎么办、以及公开发表带来的顾虑该如何权衡。
可以直接用的写作要点
- 01
公开写作是最好的名片：一位 CTO 的个人博客让求职者在面试前就读懂了公司的技术栈、代码和社区讨论，这比简历和官网都有效。
- 02
别等"足够有趣"的选题：把"我要写篇博客"换成"我有一个真实的问题要回答"，并且先想清楚分享的具体理由。
- 03
起步阶段觉得自己的想法平庸是正常的——审美总是跑在能力前面，唯一的路是继续写下去。
- 04
公开发表意味着永久记录，所以下笔时优先写对他人有用、经得起时间检验的内容，而不是情绪化宣泄或过度暴露隐私。
HN 评论精选
公开写作与开源让求职者在面试前就能深入了解一家公司，透明度本身就是吸引力。
我最近和一位写博客的 CTO 打交道的经历很有意思。我在换工作，想把职业方向转向大数据与分析，正好知道一家用 Kafka 和 Storm 做前沿分析的公司，就给那位只在 Meetup 上见过一面的 CTO 发了邮件。他答应一周后聊，我就用这一周研究这家公司，结果震惊于能了解到的东西之多——他本人在个人博客上写长篇、有思考的文章。我之前在 WineSpectator、Timeout、ShermansTravel 这些出版公司待过，它们对自家技术几乎不公开任何信息，我只能盲着进去。而这家分析公司很透明：在 GitHub 上开源了重要软件，我能读代码、读别人提的 issue；还建了 Google Groups 邮件列表，我能翻几十段公开讨论。
lkrubner查看英文原文
I just had an interesting experience interacting with a CTO who writes a blog. (If he is okay with it, I'll post his name later.) I was between jobs, and I asked myself, "Where do I want to take my career next?" and I decided that I wanted to move in the direction of Big Data and Analytics. I already knew of an analytics company that was doing cutting edge stuff with Kafka and Storm, so I sent the CTO an email (I had briefly met him once before at a Meetup). He said "Yes, let's talk" and we scheduled a talk for 1 week in the future. I had that week mostly free, so I decided to spend that time studying the company. And I was amazed and how much I could learn about the company, because this is pretty much the first company I have ever applied at where the CTO writes long, thoughtful posts on his personal blog. I have worked at WineSpectator.com and Timeout.com and ShermansTravel.com, and even though all of those are publishing firms, none of them have any public information about their technology (this is changing, slightly, in the case of Timeout.com). With each of those companies, I basically went in blind, with no idea of what they were doing. In contrast, the analytics company was transparent: they had released some important software to Github, so I was able to review the code, and read the issues that other developers had raised. They had also started a mailist on Google Groups, so I was able to read over dozens of public conversations regarding the strengths and weaknesses of their technology. And the CTO posts 2 or 3 posts each month, to his personal blog, most of the posts being long and in-depth. I read everything he had written during the last year, and so I was able to get a good sense of why he had made the decisions that he had made (why use Kafka and Storm) and where he'd like to evolve the company's technology stack. Because of all that, I felt like we were able to have a high-quality conversation (via both Skype and email). I didn't need to ask stupid beginner questions like "So, uh, what do you guys do?" The argument against blogging is similar to the (now largely discredited) argument that used to be made against open-sourcing one's own technology: if you give away the company's secrets, then your company has no unique advantages. I can recall, during the 1990s, people would look at you like you were crazy if you suggested you were going to give away part of your technology. But over the last 20 years, the whole tech industry has become much more comfortable with the idea of open-sourcing some of a company's technology. Having a public blog is a bit like having a public open-source project: it raises your exposure, and perhaps even facilitates the process whereby others can help you. And the limits of both strategies are the same: I think it is rare for a company to open-source 100% of its technology, and I think it would be rare for a CTO or CEO to share 100% of their thinking on a blog. But sharing part of the technology, or part of one's thinking, can clearly have benefits.
卡在选题上时，与其等"有趣的题目"，不如从自己真正想问的问题、以及非写不可的分享理由出发。
我想写博客，但总想不出自认为足够有趣的题目。这跟 Ira Glass 说的那个问题有关：起步阶段你会讨厌自己做出的东西——可我连自己想到的点子都不喜欢。我站点上仅有的几篇，都是因为"有博客之外的理由要分享"才写的。这也类似想创业点子的难题，那些建议对我都没用："我的软件该做什么"被改写成"去找一个问题"，pg 也说"文章不是始于陈述，而是始于一个问题"，可我想到的问题都不像能下手。所以我就不写。有什么办法能迈过这个坎、找到可写的东西？
zck查看英文原文
I want to blog, but I never really am able to come up with topics I think are interesting enough. It's related to the problem Ira Glass points out (http://zenpencils.com/comic/90-ira-glass-advice-for-beginners/), where you don't like what you're creating for a period when you're starting out -- but I don't even really like the ideas I'm having. The few entries I have on my site are things I don't think are especially interesting, but I had reasons to share them outside of "hey, a blog post", so I wrote them. This is closely related to the problem of coming up with ideas for a startup. But none of that advice has really helped me. For example, "what should my software do" is restated as "find a problem". Similarly, pg says "An essay doesn't begin with a statement, but with a question." But I don't really come up with questions that seem approachable.^1 So I don't write. Any suggestions for getting over the hump and finding things to write about? [1] Actually starting things is something I think is incredibly undervalued in society, especially for children. Growing up, I didn't even enter my mind that I could create things. I read a lot, but never wrote. Throwing off this blanket is an extremely hard process I've just started doing.
公开发表的永久性会带来真实顾虑，动笔前需要权衡隐私与表达边界。
我很想写、也想有人读我的碎碎念，但我最担心的是把东西留在公共记录里。谁知道将来会遭遇什么样的"1984 式"反噬——"你的过去就是你的全部"。我能想象未来的医保公司去翻我的博客找"冒险倾向"的痕迹，甚至自动去做。"吸烟者该多交保费"这种共识的流行趋势也很吓人，下一步会是什么？用化名写也不现实，早晚会被找到，连中本聪这种密码学天才都会被挖出来。而且我可能一时疏忽，把"有细微差别的观点"全放飞出去，被认出来之后风险更大。看看 YouTube 评论区就知道了。
wernerb查看英文原文
I'd love to write and have people read my ramblings: But putting things in the public record is my #1 concern. No-one knows what kind of 1984/'your past is all you are' backlash you might expect in the future. I see ways for my future health insurance provider to investigate my blogging for risk-taking overtones. They might even do it automatically.. The tendency for people to agree with "people who smoke should pay more for health insurance" is also scary. What's next? Anyway.. Blogging behind a pseudonym is also not really an option. I could be tracked down eventually. Even Satoshi will be outed, and he's a cryptographic genius. Also, I might lapse and let my 'nuanced opinions' go wild by accident only to be more at risk after discovery. Just look at those Youtube commenters go..
也有人持相反论调——成功者未必写博客，写博客的价值需要自己判断而非盲从号召。
我在琢磨怎么把这篇和 Keith Rabois 的那句话对上："我没见过哪个成功的 CEO 或创业者是定期写博客的。"
lmg643查看英文原文
I'm trying to reconcile this with the Keith Rabois statement: “I don’t know of a single successful CEO or entrepreneur who blogs regularly.” http://blog.asmartbear.com/ceo-blogging.html
同类还值得读
我坚持每天写一条 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 条写作要点编辑精选