Cool idea. I had similar half a year ago but I tried to build something in only one day. Of course it limited me to use only the tech I knew well because I didn't have time to learn anything. It wasn't maybe the best thing because of that but then in the other hand it was a lot of fun. I have learned that it's better to have two projects running the same time because that way you can switch the other project every time you feel bored about the current project. I try to keep the Google's rule one day a week for hobby project and rest for the main project.
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.
Cool idea. I had similar half a year ago but I tried to build something in only one day. Of course it limited me to use only the tech I knew well because I didn't have time to learn anything. It wasn't maybe the best thing because of that but then in the other hand it was a lot of fun. I have learned that it's better to have two projects running the same time because that way you can switch the other project every time you feel bored about the current project. I try to keep the Google's rule one day a week for hobby project and rest for the main project.
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.