As a single contributor how is your project managed? Do you have a to-do list?
As a single contributor how is your project managed? Do you have a to-do list?
My main worry is that nobody else will want my software, and even if they did I wouldn't know how to price it, market it, and sell it. All I really know is to code, even if it just barely passes programming convention and security checks.
I envision so much for what I'm doing, but I have no idea how to get there.
It doesn't even have to be all fancy and coded up. Any little thing would do once it demonstrates your idea.
This way you can take a break from your usual routine, learn something new that will probably help you in the long run and then when you have other app ideas you'll have the knowledge to program and market it.
I think a majority of people who write code and want to be tech entrepreneurs face this.
I myself call it: "Build it and they will not come".
I think I will dedicate a blog post to this issue and I will try to use some methods to resolve this issue.
Mainly though, from a philosophy I learnt from a career coder: I'm building it for myself to use or just for the sake of it
The above is a great way to churn out 'dumb' projects purely for the sake of building them out. Carry that momentum to the startup, if it fails, it fails.
This also makes me wonder about the mantra of some people in tech circles urging founders to "fall in love" with their startup.
This is actually a very interesting discussion. Kudos to you for being brave enough to admit that: I like to code but I just don't know what the fuck I am doing anymore.