[int3rnaut]

This was a problem I was faced with, and I decided to just do both. So far it seems like the right step if only because I'm able to learn on the fly and there's a bit of a pressure for me to actually pick up some of these things. Though it does have it's flaws.

I'll be honest, when you try both, there will be times in that journey that you completely neglect the "code learning" process because other parts of the startup and life just require all of your time and energy. And as such it gets pushed to the backburner. But you have to keep going back, and make excuses for yourself to learn something outside your comfort zone. It gets harder, not easier because by the time you start learning how to crawl, you want to learn how to run and actually help out but this is a long long process. I truthfully fear I'll never get to the plateau I want to be at, and while those fears are justifiable, don't think about it as just being able to mash code into creating a project--think about it as being able to do your part of the puzzle better. With a growing understanding of the process and tech side you'll be able to contribute, communicate, and create much more efficiently. Chip in when you can, you'll be even more appreciated, but don't be hard on yourself if it never comes. Just keep trudging forward.

A lot of tech people seem to unfairly look down on non-tech founders looking for a counterpart, even if such as in your case you bring a lot to the table, and from the moment you start your endevour you'll always be judged and perhaps ridiculed for not being part of that circle. And that will fuel you to learn, but don't forget what got you to this place in life, and why you weren't a coder to begin with, you've gained and learned many things in your life--all of which will come in handy and bring a different and unique perspective and possible answers to the pains you wish to solve.

Never stop learning. And good luck!