出版与作家生涯2022github.com编辑精选
发布你的作品会增加你的运气
Publishing your work increases your luck
导读
这篇 GitHub 指南主张：持续公开你的作品（文章、代码、副业项目），就等于扩大“运气的接触面”：机会更可能主动找上你，而不是你去找它。对写作者来说，它提供了一个不依赖天赋或人脉的长期策略：先把东西发出去，让偶然性有机会发生。评论区多位从业者用亲身经历印证了这一点。
可以直接用的写作要点
- 01
把“发布”当成日常动作：哪怕当下觉得内容无足轻重，机会常常是多年积累后才浮现的。
- 02
公开你在做什么，让潜在的雇主、合作者和读者有机会看见你；可见度本身就是资源。
- 03
在公开讨论里给出具体、可操作的帮助（推荐方案、给入门指引），一条小评论也可能被关键人物看到并转发。
- 04
诚实标注自己的真实水平，可信度比假装资深更能赢得机会；写作目标也可以是“写出我自己想读的东西”。
HN 评论精选
十年博客与开源的回报是长期积累出来的，别因为当下“没人在意”就停手。
这跟我的经历高度吻合。我写了十年博客，机会由此而来；做开源十年，机会也由此而来。大部分时间里我都觉得自己在做无足轻重、只对自己有意义的事——那是错的。稳定地把作品放出去、和其他人协作，事情就会发生。
johnny_reilly查看英文原文
This resonates with my own experience tremendously. I've blogged for ten years - opportunities have come out of it. I've worked on OSS for ten years - opportunities have come out of it. Most of the time I was doing both I felt like I was doing something inconsequential that only meant something to me. That was incorrect. Reliably putting work out there and collaborating with other humans makes things happen.
公开在做的事会把你带到机会面前：工作、读者和副业收入。
确实如此，我可以作证：“扩大运气接触面”这个说法是真的。公开你在做的事，能为自己创造很多机会。它让我在 Taylor Otwell 的事业起飞之前就和他共事，如今我在 Fly 帮助推广 Laravel。我的副业项目帮到了别人学习，也给我带来了读者和额外收入。
fideloper查看英文原文
It’s true, I can attest! The idea of “increasing your luck surface area” is real. You can create a lot of opportunities for yourself by being public about what you’re up to. It got me a job working with Taylor Otwell, before his businesses took off, and now working at Fly to help with Laravel adoption. My side projects have made helped people learn, given me an audience, and earn extra income.
一条真诚具体的公开评论就可能被关键人物看到；诚实说明自己只有教程级经验，反而增加了可信度。
我第一份付费写软件的工作，靠的是在 GitHub 上的运气。大学时我只是在一个同学的 issue 下留言——他为本地黑客松做网页应用，不知道选什么方向，也没有框架经验。我建议用 Rails，列了几条优点，还给了入门指南链接。几小时内，一位人脉很广的学生（好像是计算机社团负责人）看到我的评论，转发给了一位做本地 Rails 工作的校友。其实我除了当时的教程之外毫无 Rails 经验，也明确说了这一点；但他看好我的 GitHub，乐意把活给我。对学生来说报酬相当不错——谈到价钱时我没答上来，他直接说 50 美元一小时，而我原本预期只有一半。
hoten查看英文原文
I got my first paid work writing software because I got lucky on GitHub. Back in college, I simply commented on a peer's issue made for a local hackathon. He was confused about what direction to take for a webapp, and didn't have any experience in any frameworks. I just suggested Rails, and gave a few highlights for it and pointed him towards some starter guides. Within a couple hours a well connected student (I believe he ran the CS club) saw my comment, and forwarded it to an alumni who was doing local Rails work. I actually didn't have any experience in Rails beyond the tutorials of the day, and I made that clear. But he liked the look of my GitHub and was happy to give me the job. It was pretty good money for a college student. I recall not really knowing what to expect hourly wise, and when he brought up payment I wasn't able to give an answer so he immediately said 50/hr. To me, I was truly expecting like half of that. I tried to keep cool as I accepted. My pricing mindset was definitely anchored by waiting tables, where 50/hr is something you might get if you got a really lucky shift and required busting ass. So to get that much for _sitting down_? Oh boy. After settling on the price, he stepped out of the room for a bit. This was a shared co-working space, and I recall looking over to the guy next to us (who I could tell was paying some attention to our conversation) and saying I did not expect that much money. He happened to work for Uber - and he agreed that I got a very good deal. Not sure why I remember that detail. Anyway: yes, working in public, and even being helpful in public, certainly can pay dividends.
发布的价值不必用名利衡量，它服务于学习，以及“写出自己想读的东西”。
我公开发布作品已经几十年了，并没有带来名和利——主要是因为我对名利本来就不太感兴趣。我总体认为它是“成功”的：我做这些主要是为了学习和养成追求卓越的习惯。我写自己想用的代码，写自己想读的文字。之前还有一篇讲“把认真当服务”的帖子，和这里很契合。
ChrisMarshallNY查看英文原文
I've been publishing my work for decades. It really hasn't resulted in fame and fortune; but that's mainly because I am not particularly interested in fame and fortune. I generally think that it has been "successful." I mainly do what I do, to learn, and to develop the habit of excellence. I write the code that I want to use, and I write the prose that I want to read. There was another posting, about "Giving A Shit As A Service," and that dovetails rather well, here (in my case).
同类还值得读
写书：值得吗？
Writing a book: is it worth it?
Martin Kleppmann（《设计数据密集型应用》作者）复盘写书到底值不值：金钱回报低、耗时极长，但带来了可见度、信任和职业机会。
出版与作家生涯2020 · 642 分 · 287 评4 条写作要点编辑精选写书并不是个好主意
Writing books is not really a good idea
这篇文章讨论靠写书谋生的现实难度，评论区从版税数学、收入预期和写作目标三个角度补充了作者视角。
出版与作家生涯2021 · 577 分 · 609 评4 条写作要点编辑精选如何自助出版一本书：实用资源清单
How to self-publish a book: A handy list of resources
这是一份关于「如何自助出版一本书」的资源清单帖，涵盖从编辑、排版到 ISBN、销售渠道的实操工具与花费。
出版与作家生涯2018 · 558 分 · 88 评4 条写作要点编辑精选我自助出版一本Ruby on Rails书，赚了7万美元
How I Made $70k Self-Publishing a Book about Ruby on Rails
这是一篇 Ruby 开发者自述：他把一套 Rails 性能课程（书＋视频＋答疑）自出版，一年毛收入约 7 万美元，并总结了选题、定价、营销等经验。
出版与作家生涯2017 · 539 分 · 175 评4 条写作要点编辑精选石黑一雄警告年轻作家因“恐惧”而自我审查
Sir Kazuo Ishiguro warns of young authors self-censoring out of 'fear'
石黑一雄提醒年轻作者因“恐惧”而自我审查，即这条帖子讨论的核心。
出版与作家生涯2021 · 396 分 · 641 评5 条写作要点编辑精选