As someone who perpetually overscopes side projects and ends up biting off more than I can reasonably chew given my free time, I really love this idea. What happens with me is I start a new project, then add a new feature here and there (because coding is fun) and end up never reaching anything close to "done" then getting into analysis paralysis of what to do next because there is so much. Ultimately it gets abandoned and forgotten and put on the graveyard of all the other side projects - not that this is horrible, I do them for fun and not profit, but it would be nice to launch a few.
If OP is actually the author, a question - what was your approach in keeping the projects tightly scoped and not introducing feature creep? Deadlines or time-boxing? Pre-emptive deciding on what you will and won't do? Lowering your standards for "good enough"? Just plain old discipline? Something else?
If OP is actually the author, a question - what was your approach in keeping the projects tightly scoped and not introducing feature creep? Deadlines or time-boxing? Pre-emptive deciding on what you will and won't do? Lowering your standards for "good enough"? Just plain old discipline? Something else?