If you're the ideas guy--"the suit" or whatever slightly condescending term you're calling us now--I think you're almost always better off learning to program

If you're the ideas guy--"the suit" or whatever slightly condescending term you're calling us now--I think you're almost always better off learning to program on your own. Once you've learned enough to build a prototype, and are actually on your way or have created an MVP, you've indicated a) that you're serious about this project, b) whether it's viable going forward, and c) that you're not a complete technical neophyte. Most importantly, you've flipped the script to a certain extent -- you can now be selective about who you choose to work with, and you've qualified yourself enough to be an arbiter of quality. Just my two cents. I can understand why the developers here might hesitate to work with someone who hasn't proven that he's willing to put in the work. But on the other hand, if you're a serious non-technical co-founder, I'm not convinced it's a great idea to just pick the first developer who's willing to work with you. Seems like a recipe for disaster.