I'm in need of some advice.
I have started my own project in Sept 2007.
I've managed to just about get it to 70% complete for version 1 which I am schedule to release the beginning of April.
Along the way I've invited a few alpha testers who I knew from another site which would be a competitor. While chatting almost daily with one of the alpha testers (who is also a professional programmer as myself) I thought to myself wouldn't it be great if he were to come on board and directly help guide the ship so to speak. His many suggestions have been pretty helpful and good...although sometimes he tends to make suggestions that replicate functionalities in sites he currently frequents.
My question is, what is expected of bringing on a cofounder later in the game? How do I establish that this is my vision and things should be done my way? Or should I just not be so paranoid in fear a second coder could just screw everything up? Should there be some agreement up front about who has what stake? What precautions should I look out for? He works for a good company in Austin and from our conversations he almost seems right up my alley...so it could turn out to be a golden opportunity and not the glooms day scenario I've been painting thus far.
Any encouragement or warning would be great.
By the way...make this dialog bigger Y...its freakin too small.
We've been about 70% complete for version 1 roughly half a dozen times now. We were 70% complete in April of last year, which we actually did release (it's getting users now, but not many). We were 70% complete in October, when we sent along a demo with our YC app. But we realized that it wouldn't work for the general case, so we went back to the drawing board. We were 70% complete in November, when I realized we were rewriting things too much with each additional feature and stepped back for a week to actually design the thing. We were 70% (well, more like 50% by my reckoning) complete in December, when we switched web frameworks. We're about 70% complete now, though if this is anything like past 70%s, it's probably more like 40%. Now I don't trust any estimate that's not backed up by Trac tickets.
Always remember the 90-90 rule: "The first 90% of the work takes 90% of the time. The remaining 10% takes the other 90%."
Many startups have to go through multiple rewrites before they have something useful - Reddit's on their 3rd (though they launched with their first), I heard Xobni had to redo their first try to be more ambitious, YouTube completely revamped the site to make it stickier, my last day job went through about 4 rewrites before we launched the product (which is the 7th product it's launched...none of them really got product-market fit), the job before that changed directions 4 times in the year I was there and completely rewrote things about a half-dozen times, never actually releasing anything.
I'd look at the stuff you do now as exploratory programming; your job is to find out more about the area, so that it eventually gets to the point where it "clicks" and you can just crank out code that works. You're still very early in the product process; a cofounder could add a lot of value down the road.