[dennybritz]

I'm assuming you have an idea for a product and want someone to work with you on this. I agree with the comments that you should learn to build things. This doesn't mean you need to become a skilled programmer, but you should become familiar with the basic tools to build a first version of your product. There are a couple of reasons for this.

1. The best people are typically attracted by traction, metrics and numbers, not fluff ideas. If you can build a first version of your product and get initial traction it will be much easier to get people interested in what you're doing.

2. Putting in work shows that you're serious. For every 100 people that have "business ideas" there is maybe one that actually acts on them by investing their own time and money. This will set you apart from all the other people looking for technical co-founders.

3. It will make communication with your technical co-founder down the line easier. If you are doing anything related to software then you must understand (on a basic level) how things work and what tradeoffs and decisions go into building a product. Again, you don't need to become a programmer, but you should have enough knowledge to have an intelligence conversation with a technical person about important technical decisions. Otherwise there'll likely be a lot of frustration and bad surprises on both sides. Trust me, I've been there.

Btw, a "first version of your product" doesn't necessarily mean a be full-blown application. You could setup use a blog, newsletter, spreadsheets or whatever else to generate traction.