| I have two answers: 1.) Fuck being technical. Become a CEO. This is the more simple of the two and it relies upon a really horrible truth. Getting your product built is nothing. I'd like to say it's only half the battle, but that does the battle a disservice. At the end of the day, the difference will be whether or not you, as CEO, can hustle your way to either profitability or positive cash flow. (Profitability is better, but it doesn't sound like you're at any risk of becoming profitable any time soon.) Today, your biggest issue is that you need a technical product built. When you get the product built, you'll replace that issue with another stack of big issues, many of which are way more ambiguous than this one. So, go out there and jfgid (just fucking get it done), and hold on tight. 2.) Become technical. Want to hear another secret? I'm very technical, but I can't think of one single thing I know that an intelligent, driven person couldn't figure out in a weekend. The difference between me and you is that I've just invested more time into learning how to do these things. There aren't any magic powers involved in being technical. For me, it's really just stubbornness. Find a tutorial. Michael Hartl's Rails tutorial is quite good as it shows everything from version control through unit tests and everything in between. Go through that tutorial and then start hacking on your ideas. The first version you put out will be really bad, and in a few years, you'll be embarrassed by it. But keep going and if you enjoy the slog, you will learn. I say this with absolute certainty. If you work hard and put in the hours, you can be your own technical founder. JFGID. |