11–14 of 14 posts
Dude! You're like that guy from that "how to spot a bad non-technical co-founder" article. Pretty sure this is a troll.
Not sure who "that guy" is, but I can assure you I'm not a troll. I've been following ycombinator for a long time, I am just new to the Hacker News Section. -Jim
HOWEVER:
I strongly feel that anyone who is going to be working with or managing programmers should spend at least some time learning to code. You will not be able to do their job, but you will have a much better understanding of the basic issues involved.
As a technical person, I also have much more respect for someone who wants to talk to me about an idea they have after they have taken the effort to make some sort of rough mock-up or prototype. I may have to throw it out and start over, but it shows commitment and it shows that you have been doing some serious thinking about the problem.
You need a technical co-founder, or a technical partner/adviser you trust that can help guide development. What you miss with a development agency/contractor-only approach is the critical technical feedback loop and iterations that strengthen and develop your idea that you'd typically do with that co-founder. Agencies/contractors will say 'yes' to what you want (and are happy to take your money), absent the really rich and valuable feedback and collaboration you get from a technical partner who has a vested interest in a shared vision.
You are only 2 hours away from Raleigh which I understand is pretty good for for tech talent. (http://www.fastcompany.com/1699323/why-you-should-start-a-co...). Maybe set up shop there?