Hacker News new | comments | show | ask | jobs | submit login

Somebody else just emailed me asking basically the same question, and looking for my advice. My immediate thoughts were:

- Do you need a cofounder immediately, or can you just try and do less. I know that's easier said than done, but scale back your projects into what you think the most important pain/solution is and focus on that, and see if you can get some traction. It will be easier to convince someone else to join you if you can get some traction.

- Similarly: don't look for people to take a big leap, break it into smaller steps. Do you know anyone who would do something for an evening a week. Or hack on something at the weekend. Treat it more as a fun side-project, and people might be more excited about getting involved. Then once they are in, and you have some momentum, try and grow the committment (that's basically what we did).




I agree with this.

I'd try and learn the basics of coding, put together a prototype and get some initial feedback. It will be much better to seek a co-founder at this point, who can help you complete the product and launch it.

It's not easy, and it is going to take time but that's probably the best way to go about it.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: