Need Advice: Quitting Job to Learn to Code... (and start my business)

to be totally blunt, it sounds like you're at about the stage of most of those people who post ads on craigslist that we all laugh at: "i've got a great idea, all i need is somebody to implement it"

don't kid yourself - implementation is everything, and implementing properly is harder than you will ever imagine. if you don't even know how to code, you are nowhere near at a stage to quit your job unless you have savings to keep you afloat for at least a year. 10-15k to create your startup for you in a month or two is not a reasonable estimate.

Thanks for the reply! (as well as your other one, which I've responded to in the wrong order, ha)

I think my other reply regarding outsourcing vs doing it myself frames what you have said here perfectly.

Ultimately, I do not at all think I can learn to code in a few months or a year or even 2 (well, be as proficient as I want to be and should be anyway). I know for that a fact, just based upon myself researching and learning about all the different languages, frameworks, terminology, and so on. Even that tiny amount shows the immensity of what there is out there. To be proficient, it takes YEARS. I don't underestimate it all.

As a result, I do ultimately believe I have 2 choices: outsource or do it myself. I'm honestly leaning towards outsourcing at this point since if I need a technology guy regardless than why not get an MVP put together sooner (and better) by outsourcing?

I guess it plays off what you've quoted: "invest in what you know" and I don't know coding, so perhaps I should hire what I can afford and ultimately look for someone to join forces with myself once I've created an MVP and traction and have something to really show for myself.

I might not have the technical know-how to bring to the table, but I believe I have other valuable qualities and a great idea and vision.

Thanks for wishing me luck and I appreciate the advice.

Thank you for all the posts from everyone thus far! I really needed to have the conversation, get opinions, etc. It is so helpful.

A CPA! Kudos. I know that is not easy, my fiancee just tested for her CPA...but I would hate to see the code she would write : ) This is way before your time, but Kenny Rogers had a lyric, "Got to know when to hold 'em, and know when to fold 'em" which can extrapolate to your perceived need to do everything. You can do everything, or anything, but where do you draw the line? Janitor? QA testing? Chief Bottle Washer? I'd "hold" on running the company, but "fold" on writing the code.

If you do decide to "outsource" do you mean offshore? Perhaps Rent-a-coder isn't a bad idea, but just make sure the coder(s) are available after they write the code, have them sign a non-compete, and possibly outsource a second coder to review the code if you are not getting the warm and fuzzies from the first team. Ask for well-documented code including an overview explanation, approach, architectural considerations, and lots of comments. Ask for their best work. Again, I wish you the best and I hope that once you get your prototype up you let us all know so we can kick the tires with you.

One last thing: Stop worrying about the tech co-founder and get this project in the bag! Heck, the more you type the less likely a Tech Co-founder is going to want to come on board! Get 'er done!

Just had this pop up on my reader: http://appicurious.com/2011/10/26/inglorious-applications/#....

Like another poster alluded to, save up some money (keep your job). Interview 5+ developers with entrepreneurial tendencies, pick one, thank the others, hire the one you picked, tier their compensation on milestones.

You already founded this, so looking for a co-founder is fairly moot. Hire someone, give them a chance to shine, bring them in as a partner. If trying to force the "tech co-founder" isn't working, try something else. As for outsourcing...I think it is a silly word that means "not committed". You're not committed to them, they are not committed to you...in the end you have your prototype, but know far less about it then if you hired someone, even an intern, and had them walk you through their process and the code...most outsourced help would probably not do that for you. A less risky move is to hire someone on 1099 for the project...you probably know more about those rules than most.

If you waste too much time fretting over the details, you'll never get it off the ground. Check your balls, take the leap. You will never be 100% correct (you damned accountant! : ) so take your best shot and learn what you are made of.

Post an email link or phone number in your about and I'll give you a call and a swift kick in the ass if you need it.

You, and I and most of HN, see this conundrum every time we want to start something. In your case, since you don't have the geek chops, you have the following choices:

1) Get lucky and find a TCF willing to work for equity. 2) 'Hire' a company/freelancer to build your MVP 3) Hire someone to grow with you and build your MVP 4) Do it yourself

My opinion is that if your product is actually worth all of this fuss then you have to put your money where your mouth is. I would keep the job, read more about development, save some money, and figure out how you are going to hire someone on a project basis (1099/freelancer)...there will come a time, MVP or not, that you will have to make that leap. Sure, today is not the day. Let's say you get your MVP created, its a hit, and then what? What about hosting it on EC2 or dedicated servers? What about some marketing? What about some legal reviews? What about incorporating (kinda need that to realistically spread equity to partners and investors)? If you did outsource the MVP how are you going to get your new dev team up to speed when you do hire...and what if it needs to be rebuilt from the ground up because the outsourced dev did not take scaling, security, or authorization into account? What about the other 10,000 things that are going to hit you?

You'll be fine. I see a lot of people that have the best of intentions that are not fiscally capable of starting a business. You at least have a job. Some of these stories of creating the next whiz-bang site with 10 Million users on the first day and only $1.57 in startup capital are definitely the exception and not the rule. If you compare yourself to that success, then you are being unfair on yourself and on your future team. All of this lean startup talk ticks me off because some times you do need some capital to make it happen. That is where outsourcing may help a bit, but what ask yourself if losing the knowledge of the code is worth it? Fate's word of the day: Conundrum.