I really like this question. As a technical guy, I struggled a lot to come up with an adequate answer as a business-minded friend and I were discussing this. We

I really like this question. As a technical guy, I struggled a lot to come up with an adequate answer as a business-minded friend and I were discussing this. We almost became co-founders. I'll be interested in what others' experiences entailed. But for us, I think we deemed it simply necessary for you to have a good idea of the technical side of things. You don't need to code and interest in learning to code isn't needed. But when I talk about topics regarding code, you should at least have an idea of what I'm referring to; you are, after all, aspiring to work in a technical project. So when I refer to something like vim or memory control, you should have at least a vague idea of what I'm referring to. Brush up on that. Read a lot on technology. A good person that came up in the discussion as an example was Steve Jobs. In many ways, he wouldn't be seen as the technical partner (at least when compared to Woz), but he does seem to know and understand the overall idea behind some of the hardware he mentions, which is vital.