请问HN：在“氛围编码”的时代，独立开发者如何保护他们的作品？
我正在进行一个新的开源项目。（我的项目涉及人工智能基础设施，已经在几个知名基准测试中取得了最先进的结果。）其核心价值不仅在于代码本身，而是源于许多失败尝试、实验和设计迭代中形成的相对特定的算法方法。
我面临的困境是：
如果我早期开源，我可以获得反馈、信任、用户，甚至可能有贡献者。但这也意味着我暴露了核心设计和算法。对于大型语言模型（LLMs）来说，将一个代码库转变为不同的实现变得比以前便宜得多。
如果我保持闭源，我可以更长时间地保护我的工作，但我也失去了开源软件的主要优势：采用、审查、社区和可信度。更糟糕的是，其他人可能仍然会构建类似的东西，并成为该领域的默认项目。
我是一名几乎没有受众的新独立开发者。如果一个大型组织或知名开发者看到这个想法并推出类似的实现，他们能够立即获得比我几个月内更多的关注。最终，我为开源我的项目付出的努力可能一无所获。
作为一名独立开发者，你会如何处理这个问题？
查看原文
I am working on a new open-source project. (My project is in AI infrastructure. It already gets SOTA results on several well-known benchmarks.) The core value is not just the code, but a fairly specific algorithmic approach that came out of many failed attempts, experiments, and design iterations.<p>The dilemma I am facing is this:<p>If I open-source early, I get feedback, trust, users, and maybe contributors. But I also expose the core design and algorithm. With LLMs, turning a repo into a different implementation is much cheaper than it used to be.<p>If I keep it closed, I protect the work for longer, but I also lose the main advantages of OSS: adoption, review, community, and credibility. Worse, someone else may still build something similar and become the default project in the space.<p>I’m a new solo dev with almost no audience. If a large org or a well-known developer sees the idea and ships a similar implementation, they can get more attention immediately than I can get in months. And in the end I get nothing for open-sourcing my project.<p>How would you handle this as a solo dev?