Live data from Hacker News

You do need a technical co-founder [video]

ycombinator.com

191–200 of 381 posts

Re: You do need a technical co-founder [video]

#191

The inverse is also true. As a technical founder, and maybe even an introvert like me, you should definitely look for a non-technical co-founder who can help you with networking, etc... I found my dream co-founder through YC Co-founder match and what can I say, it's going great. We're focusing on enterprise GraphQL/API solutions ( https://wundergraph.com ) and I benefit from the networking and communication abilities…

just a heads up, i found a typo on your website :)

"Get started for free in 3 minutes No credit card required, no vendor lock-in, but the convencience of a fully managed service."

Re: You do need a technical co-founder [video]

#192
post #180
post #174

Earlier quoted context omitted.

> That said, there are different failure modes for purely technical people not understanding business. A common one, I think, is technical people thinking management or business expertise is easy (or even beneath them) because they're so smart in other areas--and any problems they might have can surely be solved with the same tools they use to solve engineering problems, right? Which is kind of the flip side of the a…

The biggest business gap seems to be assuming other people won't screw you over, given enough money on the table and the opportunity. I assume most MBAs already know this. Lots of technical people learn the hard way.

Competing with that naivete is the great delusion of technical people that "If we build it they will come."

(Speaking as an technical person who constantly meditates on that problem.)

Re: You do need a technical co-founder [video]

#193

Earlier quoted context omitted.

More people need to read https://grugbrain.dev/

I like this but I don't understand one part under "Saying OK" * sometimes probably best just not tell project manager and do it 80/20 way.* Does 80/20 in this context mean that we'll implement 80% of what is asked for an leave out the remaining complex parts?

More or less and it usually gets the job done. The last 20% can be a real time suck if it isn't managed properly.

What you don't want is for the last 20% to occupy 80% of the time.

Re: You do need a technical co-founder [video]

#194
post #176
post #135

Earlier quoted context omitted.

Windows (especially v3.1, Windows 95 and Windows XP) was leaps and bounds better than its contemporaries when it came to normal desktop use. You can have the most technologically advanced OS in the world but if it is too difficult to use for 99% of potential users then it it not a good product. Microsoft was one of the first few companies to really get this right.

Yeah, perhaps I should have said MSDOS. But even still, I think perhaps your rose-colored hindsight is probably miscoloring your memory. The initial releases of Windows was a nightmare, with Bill's mom consoling him after a particularly disasterous demo, and if it wasn't on the back of the brilliant--or lucky--marketing maneuverings that cemented MSDOS as the preeminent PC OS at the time, I firmly believe that Window…

Meh. Was early Windows (and/or MSDOS) perfect? Obviously not. Was it better than its competitors? Yes. Absolutely. Compared to what we have today they were all shit tbh and MSDOS was better than most.

Don't get me wrong, the marketing game of early MS was absolutely phenomenal. I just want to say that they succeeded to the degree they did because BOTH marketing AND the tech were good.

Re: You do need a technical co-founder [video]

#195

Even this article IMO subtly demonstrates the mindset that leads nontechnical founders to not think they need a technical cofounder, by phrasing the search for one as “recruiting” as if they were a subordinate or code monkey. It should be a partner relationship, not a subordinate relationship. This mindset that technical cofounders are essentially “coders” (a term I hate) is very prevalent among inexperienced nontech…

>> It is very frustrating when some Ivy League 25 year old PM/management consultant tries to pitch you on their vision while treating you like an idiot savant they can easily take advantage of.

I get calls weekly from people seeking technical co-founders. The biggest thing most CTO candidates dont realize is the power they have -- unless the "business co-founder" is actually bringing something to the table.

I'd LOVE to work with a "Business co-founder" who actually brings Purchase Orders, Funding, Transact-able Relationships, prior wins (esp publicly verifiable wins). That would be a dream.

It makes no sense to work with a "Business co-founder" who wants ME to put in hundreds of hours of technical work -- upfront -- often for equity "e.g., free" -- and retains the right to take all the upside and has none of the downside. Why would I need a "Business Co-Founder" at all in that case, I might as well be the only founder and recruit later.

I see tons of friends burnt by these types of "deals." The biggest red-flag is when the "Business co-founder" still has a job and no real skin in the game.

Re: You do need a technical co-founder [video]

#196

Even this article IMO subtly demonstrates the mindset that leads nontechnical founders to not think they need a technical cofounder, by phrasing the search for one as “recruiting” as if they were a subordinate or code monkey. It should be a partner relationship, not a subordinate relationship. This mindset that technical cofounders are essentially “coders” (a term I hate) is very prevalent among inexperienced nontech…

> This mindset that technical cofounders are essentially “coders” (a term I hate) is very prevalent among inexperienced nontechnical founders. I know I’m preaching to the choir here but a lot of technical people have deep industry/business/product knowledge and have social skills. It is very frustrating when some Ivy League 25 year old PM/management consultant tries to pitch you on their vision while treating you like an idiot savant they can easily take advantage of.

This is nicely worded, but I would like to expand on it. This is coming from someone who is a businessperson who programs — I’ve been programming since I was 10, but I’ve never had the job of a programmer.

tl;dr - I think that both programmers and business people can be delusional about their value add, but folks who can do both are easier to work with, and folks who can do both have more opportunities than just hyper-growth startups.

In generalities, there are four groups of folks on the tech-business continuum.

1. Pure tech folks with little or no business acumen. Some of these folks think “sales” or “marketing” are fighting words. I find many of these folks very difficult to do business with. To be charitable to the “Ivy League” folks you refer to, they have probably met enough of these pure tech folks (some of whom are actually idiot savants) such that they erroneously over-generalize to think that all tech folks are like these pure tech folks.

2. Tech folks with business acumen. The business side usually comes from experience. I think pg advocates for tech folks who do start ups to develop into this. Overall much easier to do business with, but sometimes they make product-oriented decisions that miss the forest for the trees. The best tech businesses come from this group, but they get outclassed on the business side unless they embrace the business side aggressively (Zuck and Gates being prime examples). I think the “Ivy League” folks lose a lot of business due to lack of respect for this group.

3. Business folks with tech acumen (this is me). Great at taking over tech business that are poorly run and optimizing them either as a c-suite executive or as a buyer (this is what I do). While I don’t refer to programmers as “coders”, and I don’t treat programmers as idiot-savants, I know how to find and pay programmers to solve my business problems. Interestingly, I run into some programmers who are doing commodity work who want a percentage of the business. My offer is always the same — zero. I’m not building a startup or complex software. Their skills are largely fungible to me, since most of the value is in finding the solution rather than the nuts and bolts of development. The exception is for folks in group 2 who want to move to group 3, but at that point they become a businessperson rather than a programmer.

4. Business folks with no tech acumen. These are the “Ivy League” folks (and a lot of VCs, tbh). These are the “idea people”, the people who are clueless about tech and tech development, often the people who are also bad at business, but they happen to have access to money and/or critical buyers. Fwiw, many of these folks treat other business people even worse than programmers — they just treat most people like idiots, sans the savant. I sometimes have a hard time doing business with these folks, because they frequently don’t know the value (or lack thereof) of their business, and/or they are only looking for suckers to do business with. Many/most of these folks are all style and no substance. If they had some substance, they would be in group 3 (or try to be).

Obviously these are people on a continuum that are separated into somewhat arbitrary groups. That said, these archetypes exist.

How do these archetypes matter for tech businesses?

If you’re in group 1, you’re at the mercy of whatever business person you can work with. You hope that you end up more like Woz than most of the pure tech folks who get restructured out as the business grows. I strongly recommend that the pure tech folks focus on getting paid primarily in cash rather than equity, since any non-benevolent business person will structure out the tech person’s equity as soon as possible.

If you are in group 2, you are in a strong position to develop a successful startup or successful tech business. Just realize that you are a cog in the VC machine, and they only value you for your potential to hit home runs. You can make more reliable money (think 8 or 9 figures) in a “lifestyle business”, but it is not likely you will become a billionaire… unless you shift to group 3.

If you are in group 3, you need to realize that most of your value will be by doing very boring shit. Billionaire status is possible, but it will be a boring trip, and you are not likely to appear in any sexy tech write ups unless you engage in aggressive self-promotion in these areas (some should, most probably shouldn’t). The biggest mistake I see group 3 folks make is to think that they are in group 2, especially if/when they try to develop a consumer-oriented product without getting a group 2 cofounder.

Group 4… well, group 4 is what they are. There is some jiujitsu by which their egos and ignorance can be used for greater good. If you engage with these folks, I would only do so with that type of interaction in mind. If you engage with them on their terms, you will almost certainly lose.

Why did I write all of this? To clarify options for various level of tech people.

The HN/Ycombinator narrative to push for technical co-founders is very valid for start ups (the pg kind that are built to grow fast), but there many other ways to make money as a tech person or a tech-oriented business person than start ups (especially now in the 20s compared to the 90s or 00s), and some/many of these are more reliable ways to get to a “fuck you money” level. I don’t think a lot of highly skilled tech folks realize this.

Re: You do need a technical co-founder [video]

#197
I'm a technical founder working in a deep-tech startup.

If I am completely honest, I think the recommendation of having a technical cofounder while useful for startups in the past might not be as useful for the startups of the future.

Why? I strongly believe AI will cause a paradigm shift, and I'll adventure stating that AI will make non-technical people be able to do more and more with less. Which will make the requirements for differentiation in the tech side even harder to accomplish (very few people reaching the god-tech realms), but at the same time it would make the bases reachable for almost anyone. Basically, a more polarized order where less people will have access to "technical founders" that can differentiate themselves enough outside of the AI realms.

I'd love to get more thoughts on this!

Re: You do need a technical co-founder [video]

#198
post #120

Earlier quoted context omitted.

I love the way you put this. It also doubles as a great explanation for why programmers shouldn't be worried that ChatGPT is going to steal their jobs: ChatGPT is good at the garble of weird text, but it's terrible at the "wrangling systemic complexity in a good, sustainable and reliable way" piece.

You know what computers couldn’t do 10 years ago? Understand and write coherent code. Why do you feel confident in your opinion that they won’t be able to do that in the next 10 years?

If they can "wrangle systemic complexity in a good, sustainable and reliable way" then I think that's AGI. If we hit AGI we'll have plenty of other things to worry about beyond being able to make a living as programmers.

Re: You do need a technical co-founder [video]

#199
post #185

Earlier quoted context omitted.

Why would you want a nontechnical cofounder to do these 3 specialized full-time roles? Is this a serious question? > but if you have some money lol . Just… lol.

yes. why would you want the three people doing those three specialized full-time roles to be nontechnical? it seems to me that, given a nontechnical person who's good at one or more of those roles, they'd obviously be even better at it if they also understood the technology. ignorance and incompetence are weaknesses, not strengths as for having some money, the context of this discussion is startups with angel or vc f…

Because good luck finding those three roles where they’re from a technical background?

I’ve worked with a grand total of one PM who was from a technical background. He was actually a great engineer but he was absolutely the exception to the rule.

Sure, if you can flesh your team out with entirely technical people filling those roles, great for you, but that’s like asking why you wouldn’t only hire 10x engineers. Well of course if you could find and hire only 10x engineers you would, but it doesn’t work like that. Especially considering those are all industry positions that are typically taken by people who never went into technical roles.

Re: You do need a technical co-founder [video]

#200

Corollary: you do not need a non-technical co-founder. My advice to engineers is that it's nearly always easier to learn business/sales than to learn to like a co-founder, especially the type generally drawn to being a "business" founder. It is good to have a co-founder in general though, get one of those if you can. Just don't worry about finding complementary skills, bias entirely towards someone you can work with.

> My advice to engineers is that it's nearly always easier to learn business/sales

Technical people mispredict the value of a business co-founder in a similar way to how this video talks about tech co-founders being misvalued. Cue jokes about sales-droids. But there is a mirror between businessy people undervaluing tech and tech undervaluing business.

A key point of the video is recruiting (albeit a form of sales): it is hard to sell "adventure" and belief.

We see this every time an engineer tries to shift to a managerial rôle and fails. In theory business skills can be learnt, in practice it is hard and perhaps easier to co-found with someone with the skills already. There are risks, but if you can't judge ability and integrity then you're already hosed.

The best example I can think of who cogently explains how they learnt is Jim Keller - talking about how he changed AMD.

Post reply on HN