Hacker News Reader

My advice to people looking for a "technical cofounder" is always to learn to code—and not in a snarky, "learn to build it yourself" way. Having even a cursory ability to code and a CS50 level understanding of computers will give you enough context to vet the plausibility of ideas, and give you the ability to articulate them in terms that might interest an engineer, as opposed to just saying "An app for investing in real estate."

View on HN

I spent years doing this, but I would still need / want a technical co-founder for my ideas.

Now I'm a technical manager who can code pretty well, but that's not really all that helpful to launch something legit and complex.

>> My advice to people looking for a "technical cofounder" is always to learn to code—and not in a snarky, "learn to build it yourself" way.

> I spent years doing this, but I would still need / want a technical co-founder for my ideas

There's two reasons why a non-technical founder should learn to code:

1: To get past the "computers can read minds" trap, and to have a high level understanding of what's going on under the hood. (Elon Musk knows an awful lot about how his cars work.)

2: For the same reason CTOs need to understand topics like product-market fit.

Reply on news.ycombinator.com