3 ms·
GhostHub hit 10K lines – now I'm burning out. What would you do?
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.
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.
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.
I’m curious how other solo or small-team devs manage this:
- How do you balance delivering new features with preventing burnout?
- When do you decide to ship versus taking time to polish your code?
- Do you continuously refactor, or save cleanup for later?
Would appreciate hearing any experiences or advice from others who’ve tackled similar challenges.
Github (For Context): https://github.com/BleedingXiko/GhostHub
- turtleyacht 1y agoAdding GitHub Actions workflows may help offload some of the toil. It should be pleasant to make small (or large) changes, not stressful.
- BleedingXiko 1y agoThat’s actually a great idea, thanks! never really used github outside of very basic version control.
- mmarian 1y agoI can't give a good answer to your question, but I do wonder why you're still working on it if a) it makes you burn out, and b) doesn't look like it has much traction (103 stars). Burn out often is caused by the fact that you don't see the value of things.