GhostHub 达到了 10,000 行代码——现在我感到精疲力竭。你会怎么做？
我正在开发GhostHub，这是一个基于滑动操作的个人媒体库服务器。它不需要账户或设置，只需运行即可立即分享。它具有实时观看同步、匿名聊天和自动索引功能，并提供缩略图预览。
在最近发布1.2版本后，我计划直接投入到更具雄心的功能开发中，比如转码和配置服务器。但管理带宽优化、Docker构建、用户界面/用户体验改进以及后端优化开始对我这个独立开发者来说变得有些不堪重负。
GhostHub的代码已经超过了1万行Python和JavaScript，不包括前端的HTML和CSS，项目开始超出我的承受范围。每个新功能都需要大量测试，我感到经典的职业倦怠正在悄然袭来。
我很好奇其他独立开发者或小团队是如何应对这些问题的：
- 你们是如何平衡推出新功能与防止职业倦怠之间的关系？
- 你们何时决定发布产品，何时又选择花时间来打磨代码？
- 你们是持续重构，还是将清理工作留到后面？
非常希望听到其他经历过类似挑战的人的经验或建议。
GitHub（供参考）：https://github.com/BleedingXiko/GhostHub
查看原文
I’ve been developing GhostHub, a swipe-based media server for personal libraries. It doesn’t need accounts or setup; just run it and share instantly. It has real-time viewing sync, anonymous chat, and automatic indexing with thumbnail previews.<p>After recently releasing version 1.2, I planned to dive straight into more ambitious features like transcoding and a config server. But managing bandwidth optimization, Docker builds, UI/UX improvements, and backend refinements has started to become overwhelming for a solo developer.<p>GhostHub is already at 10K+ lines of Python and JavaScript, excluding the front-end HTML and CSS, and it’s beginning to outgrow me. Every new feature demands a ton of testing, and I’m feeling the classic burnout creeping in.<p>I’m curious how other solo or small-team devs manage this:<p>- How do you balance delivering new features with preventing burnout?<p>- When do you decide to ship versus taking time to polish your code?<p>- Do you continuously refactor, or save cleanup for later?<p>Would appreciate hearing any experiences or advice from others who’ve tackled similar challenges.<p>Github (For Context): https://github.com/BleedingXiko/GhostHub