Yeah, I also had some thoughts about the duration. One day is very short for me, but one month is too long, because boredom and "too much features" would kick in. Therefore I use the one week approach. Some core features, but not too many to get drawn into perfectionist-mode.
My plan is to build one project per week, at the same time I collect feedback for the old projects and try to make them better due this feedback.
This is also an awesome rejection therapy: getting used to the fact, that probably no one cares about my stuff. And that's okay, nothing to be worried about.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks @lankinen .
Yeah, I also had some thoughts about the duration. One day is very short for me, but one month is too long, because boredom and "too much features" would kick in. Therefore I use the one week approach. Some core features, but not too many to get drawn into perfectionist-mode.
My plan is to build one project per week, at the same time I collect feedback for the old projects and try to make them better due this feedback.
This is also an awesome rejection therapy: getting used to the fact, that probably no one cares about my stuff. And that's okay, nothing to be worried about.