未完成项目的代价：重新评估你的业余工作
三年前，我的 GitHub 账户里有 34 个未完成的项目。我称之为“公开构建”。我的治疗师却给它起了别的名字。
去年，我完成了一个。就一个。一个枯燥的命令行工具，解决了我个人的痛点。400 行 Go 代码。直到有人要求，我才写了 README。没有博客文章。没有推特话题。这个项目让我得到了一家我一年前根本不可能面试的公司的高级工程师职位。
那另外 34 个呢？我上个月把它们都删掉了。
这不仅仅是关于代码。它关乎专注、影响力，以及生产力那令人不安的数学计算。让我们来分析一下。
“公开构建”的错觉
“公开构建”——分享未完成项目以获取曝光度——已成为现代开发者文化的基石。这很诱人：发布一个半成品应用，获得点赞、评论和关注。但真正的代价是什么？
我曾经认为数量等于质量。我列出的项目越多，我的简历看起来就越亮眼。但问题是：未完成的项目不计算在内。它们不会为开源生态系统做出贡献，不会解决实际问题，也不会让面试官印象深刻，除非你能解释为什么放弃它们。
GitHub 垃圾箱
GitHub 已经成为一份数字简历。但一个充斥着废弃项目的仓库会说什么？它会说你缺乏执行力。它会说你容易分心。它会说你重视曝光度胜过实质内容。
我承认，“公开构建”最初的快感能让人难以抗拒。你发布一个仓库，突然就加入了社区。人们评论、提供建议，甚至贡献代码。这感觉很棒。但长期影响呢？微乎其微。
令人不安的数学计算
让我们来算算。假设你每周花 10 小时在业余项目上。一年就是 520 小时。如果你有 34 个未完成的项目，平均每个项目需要 15 小时。
现在假设你每年完成一个项目。那 520 小时本可以投入到单个、打磨精良的产品中。
令人不安的是：那 34 个项目中，大多数永远不可能完成。它们只是半成品想法，从未真正落地。但一个项目呢？如果做得好，一个项目对你的职业生涯可以产生乘数效应。
专注的力量
当你集中精力时，时间的投资回报率（ROI）会飙升。一个精心执行的项目比十几个半成品更有价值。原因如下：
- 更深技能：完成一个项目会迫使你精通其细节。在 400 行代码中，你学到的知识比在 34,000 行半写代码中更多。
- 影响力：一个完成的项目可以被使用、审查和引用。它会在社区中建立你的声誉。
- 机会：雇主不关心你的 GitHub 垃圾箱；他们关心你做了什么。一个打磨精良的项目是一个话题引子。一个未完成的项目只是一个注脚。
案例研究：那个让我获得工作的命令行工具
让我分享另一个例子。几年前，我构建了一个命令行工具来自动化我在工作中重复的任务。它很丑，没有文档，几乎没什么功能。但它解决了我实际的问题。
我从未分享过它。我从未写过博客。我从未在推特上提过它。但当我获得现在这份工作时，面试官问我 GitHub 的情况。我给他们看了那个命令行工具。
他们很喜欢它。不是因为它很漂亮，而是因为它展示了主动性、问题解决能力和执行力。他们看到一个不仅梦想，而且能执行的开发者。
那个有所有缺点的项目，让我得到了工作。那另外 34 个项目？它们无关紧要。
如何精简
如果你有未完成的项目充斥着你的 GitHub，以下是该怎么做：
- 诚实：问问自己为什么保留每个项目。它有什么作用？可以改进吗？还是只是在占空间？
- 优先级：只保留与你的职业目标一致的项目。如果一个项目不能帮助你成长或解决问题，它就是删除的候选对象。
- 完成一个：选择一个项目并完成它。别担心完美。先完成再说。第一步最难，但一旦开始，你会发现势头。
- 记录：添加一个 README，写一篇博客文章，并在社交媒体上分享。完成的项目值得认可。
总结
“公开构建”可以是一个强大的工具，但很容易只见树木不见森林。未完成的项目不会提升你的职业生涯；完成的项目才会。
集中你的精力。优先处理你的工作。记住：重要的不是项目的数量，而是你完成项目的实际影响。
数学很简单：一个打磨精良的项目比三十四个未完成的项目更有价值。问题在于：你会选择哪一个？
The Cost of Unfinished Projects: Reevaluating Your Side Work
Three years ago, I had 34 unfinished side projects in my GitHub. I called it "building in public." My therapist called it something else.
Last year, I finished one. Just one. A boring CLI tool that scratched a personal itch. 400 lines of Go. No README until someone asked for one. No blog post. No Twitter thread. That one project got me a staff engineer offer at a company I couldn’t have interviewed at eighteen months earlier.
The other 34? I deleted them last month.
This isn’t just about code. It’s about focus, impact, and the uncomfortable math of productivity. Let’s break it down.
The Illusion of "Building in Public"
The concept of "building in public"—sharing unfinished projects to gain visibility—has become a cornerstone of modern developer culture. It’s appealing: post a half-finished app, get likes, comments, and followers. But what’s the real cost?
I once believed that quantity equaled quality. The more projects I listed, the more impressive my portfolio seemed. But here’s the problem: unfinished projects don’t count. They don’t contribute to open-source ecosystems, they don’t solve real problems, and they don’t impress interviewers unless you can explain why they were abandoned.
The GitHub Hoard
GitHub has become a digital resume. But what does a repository filled with abandoned projects say? It says you lack follow-through. It says you get distracted. It says you value visibility over substance.
I’ll admit, the initial dopamine rush of "building in public" is hard to resist. You post a repository, and suddenly you’re part of a community. People comment, offer advice, and even contribute. It feels good. But the long-term impact? Minimal.
The Uncomfortable Math
Let’s do the math. Suppose you spend 10 hours a week on side projects. That’s 520 hours a year. If you have 34 unfinished projects, that’s 15 hours per project on average.
Now, suppose you finish one project per year. That’s 520 hours of work that could have gone into a single, polished product.
Here’s the uncomfortable part: most of those 34 projects would never have been finished. They were half-baked ideas that never saw the light of day. But one project? That one project, if done well, can have a multiplicative effect on your career.
The Power of Focus
When you focus your efforts, the return on investment (ROI) of your time skyrockets. A single, well-executed project is worth more than a dozen half-finished ones. Here’s why:
- Deeper Skills: Finishing one project forces you to master its intricacies. You’ll learn more in 400 lines of code than in 34,000 lines of half-written code.
- Impact: A completed project can be used, reviewed, and cited. It builds your reputation in the community.
- Opportunities: Employers don’t care about your GitHub hoard; they care about what you’ve built. A polished project is a conversation starter. An unfinished one is a footnote.
Case Study: The CLI Tool That Got Me Hired
Let me share another example. A few years ago, I built a CLI tool to automate a repetitive task I faced at work. It was ugly, it had no documentation, and it was barely functional. But it solved a real problem for me.
I never shared it. I never blogged about it. I never tweeted about it. But when I got my current job, the interviewer asked about my GitHub. I showed them the CLI tool.
They loved it. Not because it was pretty, but because it showed initiative, problem-solving, and follow-through. They saw a developer who didn’t just dream but executed.
That one project, with all its imperfections, got me the job. The other 34 projects? They didn’t matter.
How to Cut the Fat
If you have unfinished projects cluttering your GitHub, here’s what to do:
- Be Honest: Ask yourself why you’re keeping each project. Does it serve a purpose? Can it be improved? Or is it just taking up space?
- Prioritize: Keep only the projects that align with your career goals. If a project doesn’t help you grow or solve a problem, it’s a candidate for deletion.
- Finish One: Pick one project and finish it. Don’t worry about perfection. Just get it done. The first step is the hardest, but once you start, you’ll find momentum.
- Document: Add a README, write a blog post, and share it on social media. Done projects deserve recognition.
The Takeaway
"Building in public" can be a powerful tool, but it’s easy to lose sight of the forest for the trees. Unfinished projects don’t build your career; finished projects do.
Focus your energy. Prioritize your work. And remember: it’s not the number of projects that matters. It’s the impact of the ones you complete.
The math is simple: one polished project is worth more than thirty-four unfinished ones. The question is: which will you choose?
