A non-technical founder who takes the time to learn rudimentary coding and actually puts something together is much more attractive to potential technical co-founders.

Not because they expect you to actually do any of the real coding work, but because it shows you're willing to dig in, step way the fuck out of your comfort zone, and do the really hard work required to succeed at the startup.

The devil is in the details, be it the code itself, figuring out the business processes that you're abstracting and implementing in the code, the legal nitty gritty, fundraising, etc.

It's not uncommon for non-technical cofounders to inadvertently signal that they intend to the be the high-level idea guy and hire other people to figure out how to make their ideas work, starting with their technical co-founder. But that's a big turnoff to good engineers.

Having said that, you should probably do both. There's a shortage of engineers right now and it will probably take a while to find one, so definitely better to start sooner in the process. Spend half your time networking and looking for a co-founder.

However, it could take a long time to find one, and it would probably behoove you to learn and build during that time, even something rudimentary. Start with HTML + CSS + Javascript + Node.js, which is probably the easiest web stack to get started with (only one actual programming langauge to learn, Javascript, which you can use both in the browser and an in Node.js on the server).

... Hmm, had more, but it's slipped my mind, drawing a blank now. Will continue if/when I remember it.