3 ms·
I know what it's like to be you. In the long run, you and your future projects will benefit far more from #1. There are plenty of reasons why waiting X amount
by vqc 12y ago
I know what it's like to be you. In the long run, you and your future projects will benefit far more from #1.
There are plenty of reasons why waiting X amount of time will ultimately have little impact on the success of your product. And even if someone launches first, there are plenty of ways that you can still win.
Moreover, based the scope you described in the linked post, it's likely you could learn to chop together what you're looking for within two months of hard work. There are more than enough tutorials on related subject matter that you could use to piece together a functioning version of what you're hoping to achieve.
Go with #1; hope for #3; meh on #2. (I hope someone disagrees and gives you a good alternative viewpoint.)
- echoneptune 12y agoI would second this advice of staying away from #2. We tried option #2, but it required a lot of handholding. Not to mention the risk of contractors doing the minimum amount of work to meet requirements. Also, after the contract ended, we were left with nobody in our team with enough knowledge of the code to modify it quickly. The process of reading and learning the code (and to merge it into your own thought process) can take as long as writing the code itself.
- shenghua 12y agoThanks, that was the scenario I was afraid of.
- shenghua 12y agoThanks, I just started with Raywenderlich for lack of alternative, but also for the independence. Thanks for the encouragement.