An advise to founders who can't code If you are a business/idea guy and looking for a technical co founder, stop. Stop right now. Take 6 months off and go learn how to code (day and night, weekends including). Most web apps do little besides save, show and update data. No, You will NOT become an engineer, programmer, or web developer, but you will be able to put a prototype of your idea together and maybe get one or two beta users for feedback. At this moment it will be much easier to recruit a technical cofounder. The reason why most technical cofounders can create great products is not because they have a deep domain knowledge or they are great hackers. The reason is (beside passion for the problem) their cost is time. Your cost is money. They can spend one year working after hours to create a product. Can you pay someone for one year to create a product? They can fail 23 times and still find time to build their next idea. Can you convince your best friend to work on your 4th idea, when the previous 3 failed? Here is the thing, 1 year from now, you will still have plenty ideas. But are you going to have ideas and the ability to implement them (or parts of the solution), or are you going to post one of those "Revolutionary Disrupting Idea with potential to make millions. Need Someone to build. Will give 15 % of revenue". Stop and go learn. Worst case scenario, your future technical founder will respect you for trying, and you in return will truly appreciate their skills. Note 1: If your idea is to build something truly technically challenging, then scratch my advice. Note 2: Off course all the above would mean little if I wasn't the marketer/business/idea/support/whatever guy who spent the past few months learning. Email me if you are learning, maybe we can keep each other motivated. |
You will also be able to have an intelligent conversation with a developer.
I get sad whenever I encounter a business person with no technical bullshit filter. Not because I'm judging them, but because if I can bullshit them, any other developer can. Which probably means there's a problem somewhere that will hurt all of us.
I'll make a point to have a cursory understanding of financial statements, market segmentation, and project management if you do the same for the basic building blocks of software applications. Then the two of us will be able to talk about almost anything. OK?