Re:How can a non-hacker (with very basic C++ knowledge only)...
by SwellJoe on Tuesday April 17, 2007 @06:34PM
(#13834)
Forget about C++. Learn a high level language that has the libraries you need for building an application quickly. Someone suggested Ruby, and he's not wrong. Python is another good choice, though it doesn't have an obvious "guided path to success" the way RoR works for Ruby. PHP will allow you to find a lot of potential co-founders, but it's probably not worth it...at this stage you don't have the know-how to recognize a good PHP developer, and a bad one will simply kill you (PHP is perhaps the best language for writing horrible code--the majority of stuff out there written in PHP is really frighteningly bad). That's not to say there aren't bad Ruby and Python developers...but the barrier to entry seems high enough to keep out most of the riff raff.
Find a co-founder who likes your ideas and trusts you'll get up to speed on whatever bits of the equation he/she doesn't want to handle. In a startup past the very earliest "get-to-prototype" stages there's a roughly even split between the sucky non-tech stuff and the actual development...you could take the non-tech stuff and leave the hacking to your co-founder. I'm quite technical and have developed a lot of software in the past ten years, but I found an even better developer and took on the sucky stuff while leaving him to handle most of the development. It's working very well (though I often find myself wanting to get back to real "work" when I'm doing the boring accounting/marketing/taxes/funding/support/etc. stuff--I have to remind myself that if we reach our goals I'll be able to hack anytime I want, in between rides on my robotic dinosaur, of course).
Find a co-founder who likes your ideas and trusts you'll get up to speed on whatever bits of the equation he/she doesn't want to handle. In a startup past the very earliest "get-to-prototype" stages there's a roughly even split between the sucky non-tech stuff and the actual development...you could take the non-tech stuff and leave the hacking to your co-founder. I'm quite technical and have developed a lot of software in the past ten years, but I found an even better developer and took on the sucky stuff while leaving him to handle most of the development. It's working very well (though I often find myself wanting to get back to real "work" when I'm doing the boring accounting/marketing/taxes/funding/support/etc. stuff--I have to remind myself that if we reach our goals I'll be able to hack anytime I want, in between rides on my robotic dinosaur, of course).