Live data from Hacker News

Stop Looking for a Technical Co-Founder, Learn to Code Yourself

ror.kateray.net

71–80 of 86 posts

Re: Stop Looking for a Technical Co-Founder, Learn to Code Yourself

#71

As a "non-technical" person who has had success finding "technical" people to work with, instead of trying to learn to code: 1. Become a domain expert - know the problem you are trying to solve inside and out. Know the market size, sales cycles, etc. Make connections in the industry. 2. Find Customers - Bring an idea, along with a 14,000 name mailing list that you generated via blogging on the subject. 3. Bring a des…

Great post. I just forwarded it to the 1,000 people on the co-founders meetup mailing list (http://www.meetup.com/Co-Founders-Wanted-Meetup/)! It explains very clearly the value a business person can bring, and debunks the idea that busines people are worthless. Thanks.

Re: Stop Looking for a Technical Co-Founder, Learn to Code Yourself

#72
People always bring up Jobs and Woz in these discussions. IRS a useful example, but not as an example of fate or extraordinary luck. It's a great example of one of the most common, reliable ways to find a technical cofounder. Jobs immersed himsel in his local tech scene, where he met Woz and started working on stuff with him. Rather than mythologized or fetishizes the pairing, is it so strange to think Jobs might have checked everyone out, ascertained that Woz was the best guy there, and then chose him as his guy? Sure they became friends and all, but I think it's important to realize Jobs made a deliberate choice when he started hanging out with Woz. He wasn't groaning about not being able to find a dev, he went and met them all, spotted the best guy, and started a company with him.

Jobs chose Woz. If you can't find good people and get them on board with your plan, no web app or meetup will save you. Go out. Meet people. Choose the best guy whose company you enjoy and make friends.

Re: Stop Looking for a Technical Co-Founder, Learn to Code Yourself

#74

As a "non-technical" person who has had success finding "technical" people to work with, instead of trying to learn to code: 1. Become a domain expert - know the problem you are trying to solve inside and out. Know the market size, sales cycles, etc. Make connections in the industry. 2. Find Customers - Bring an idea, along with a 14,000 name mailing list that you generated via blogging on the subject. 3. Bring a des…

I agree. For the last year I've been beating myself up because I can't code, and have tried teaching myself for years...something just doesn't click for me. But, I have HUGE respect for devs. I honestly am amazed at the stuff my staff developer can do. At a certain point I just had to give and say, "Well, I just need to make sure I can attract good developers and treat them like the wizards that they are". As a "non-…

Specific to you, I think you just added value to yourself even though you failed at trying to code because the act of trying to learn how to code itself made you discover that it's not as easy as it looks for just anybody, and thus make you appreciate your technical team better.

Not understanding what it takes makes it harder for non-technical people to appreciate talent. You could use your failure here as your selling point.

Of course, now non-technical "frat-boys" here are going to wave the "I tried and I failed" flag, but know that it's not hard for technical people to find out if you really tried or not.

Re: Stop Looking for a Technical Co-Founder, Learn to Code Yourself

#75
post #9

Jeeze, I'm doing my best here, C is hard! I will say no single effort has been more enlightening to me regarding computer science than trying to understand C. I highly recommend it to anyone with any programming experience.

Don't tell me you're learning C first? Good luck!

After PHP and JS, which are a great introduction in my opinion.

Re: Stop Looking for a Technical Co-Founder, Learn to Code Yourself

#76
I hate to be a naysayer, but this often-expressed sentiment (by pg himself no less, if memory serves) seems somewhat absurd. Perhaps I am a slow learner, but it took me roughly 6-10 years of writing software, learning programming languages, studying CS fundamentals, learning about libraries, APIs, network protocols, character encodings, security and too many other things to enumerate until I really felt comfortable in my ability as a programmer. The first programs I ever wrote were awful; I looked at them again for the first time in years a while back and was shocked at how bad they were. Even after picking up a programming language or two and learning just enough other stuff to be dangerous, my code was still crap, albeit better crap. It wasn't until years later that I was regularly producing what I now consider to be "good code."

The spirit of this post is admirable, but rather than producing more successful startups it will likely only spur the unqualified but ambitious to create nasty spaghetti-coded PHP monstrosities with gaping security holes, which will only serve to make the public at large less trusting of web apps and startups in general. Steve Huffman was a Real Programmer when he wrote the first version Reddit; heck, he even used Common Lisp! ... and he also stored user passwords in plain text. Imagine what those with even less knowledge and skill are capable of doing.

In closing, the people here are either: a) much smarter than I am and much faster learners; b) trying to falsely give others the impression of (a); c) too optimistic; d) or don't remember how bad a programmer they were when they first started.

Re: Stop Looking for a Technical Co-Founder, Learn to Code Yourself

#77

As a "non-technical" person who has had success finding "technical" people to work with, instead of trying to learn to code: 1. Become a domain expert - know the problem you are trying to solve inside and out. Know the market size, sales cycles, etc. Make connections in the industry. 2. Find Customers - Bring an idea, along with a 14,000 name mailing list that you generated via blogging on the subject. 3. Bring a des…

To be fair, the author attended the NYC YC Q&A. I imagine that there is a dearth of programmers relative to the number of people who want to start projects over there.

Re: Stop Looking for a Technical Co-Founder, Learn to Code Yourself

#78
post #74

Earlier quoted context omitted.

I agree. For the last year I've been beating myself up because I can't code, and have tried teaching myself for years...something just doesn't click for me. But, I have HUGE respect for devs. I honestly am amazed at the stuff my staff developer can do. At a certain point I just had to give and say, "Well, I just need to make sure I can attract good developers and treat them like the wizards that they are". As a "non-…

Specific to you, I think you just added value to yourself even though you failed at trying to code because the act of trying to learn how to code itself made you discover that it's not as easy as it looks for just anybody, and thus make you appreciate your technical team better. Not understanding what it takes makes it harder for non-technical people to appreciate talent. You could use your failure here as your selli…

Yes, even though I've failed to catch on each time I've tried, I keep picking up more and more of the concepts/lingo.

I do all the mockups and am orchestrating the product development, but the more I learn about programming the more I learn that a single extra box on my "mockup" can mean hours and hours on the backend.

It's so easy to do a mockup and say, "this is how it will work"...turning that into an actual application is where the magic is.

Re: Stop Looking for a Technical Co-Founder, Learn to Code Yourself

#79
post #74

Earlier quoted context omitted.

Specific to you, I think you just added value to yourself even though you failed at trying to code because the act of trying to learn how to code itself made you discover that it's not as easy as it looks for just anybody, and thus make you appreciate your technical team better. Not understanding what it takes makes it harder for non-technical people to appreciate talent. You could use your failure here as your selli…

Yes, even though I've failed to catch on each time I've tried, I keep picking up more and more of the concepts/lingo. I do all the mockups and am orchestrating the product development, but the more I learn about programming the more I learn that a single extra box on my "mockup" can mean hours and hours on the backend. It's so easy to do a mockup and say, "this is how it will work"...turning that into an actual appli…

I've heard non-programming web designers say, "I've designed this app. Now all I need is to have it coded up" (as though the back-end is merely icing on cake and that the heavy lifting is already done).

disclaimer: I'm mostly a back-end person, and I appreciate how difficult it is to not have sense of design, and I don't take good design work for granted.

Post reply on HN