3 ms·
I love it, Gabe. I've been running Hackers and Founders Silicon Valley for several years, and this flow chart pretty much nails it. I would suggest at the "Hav
by iamelgringo 16y ago
I love it, Gabe. I've been running Hackers and Founders Silicon Valley for several years, and this flow chart pretty much nails it.
I would suggest at the "Have a Hacker Founder?" level, to add a "learn how to code" box. I run in to a lot of BizDev people at our events, and the business people that have had the most success are the ones that...
1. Learn how to code. It proves to hacker founders that you are serious, and every level of technical knowledge that a business person brings to the table makes them exponentially more valuable to the technical founder.
I'm not blithely saying this. My day job is as a nurse, and I went back to school for software engineering because I wanted to do the startup thing. It took me years, but I decided early on that I was going to have to build 10 startups before one succeeded. So, I learned what I had to, to be able to build 10 startups without breaking the bank. And, they key factor there was learning how to code.
2. Leave their idea behind. Instead help hackers take their too technical ideas and turn them into proper businesses.
3. Learn how the open source model works and give away their ideas and advice freely to hacker founders. Eventually, if the've helped enough hacker founders, they gain enough street cred, karma and friendships that hacker founders will ask you to join their startup.
-----------
When I tell business people to "learn how to code" the most common response I hear is that "it takes too long". To which I say, It's going to take you at least 6 to 12 months to find a technical co founder, even in Silicon Valley, if you're lucky. You might as well start learning how to code while you're looking.
- iamwil 16y agoThis is true. Nothing gets my attention more than non-technical people that learned how to code, and even if it's not the world's most brilliant code, it demonstrates umph and a willingness to do what they can for their business and for understanding. Having learned how to code will also give you perspective, even if you're not going to be doing it later in the company. When you've broken your back coding, you'll realize that no feature is ever 'trivial', among other things. It'll make you get along and understand your technical team a lot better.