I am 100% serious, by the way. People have the most ridiculous ideas about why things failed and how it will totally work next time. If they just follow these ego-comforting steps that don't even begin to address the problem.
My top at-a-glance eye-roller says "technical co-founder quit & pulled the code out from under me".
So completely neglectful of basic business structuring that the tech co-founder could just walk away with the code, to which you don't have copyright claim? If a non-technical co-founder can't even bring responsible management to the table, why are they at the table?
Article goes on to suggest that if the non-technical co-founder had learned to code so as to not feel so helpless, things would have gone better. Just wow.
At a startup (before traction, employees, etc.), you are pretty much doomed if your technical cofounder quits even if you've structured the company with vesting, ownership of IP, etc. All the domain knowledge, architectural knowledge, etc. goes out the window when the person who wrote all the code leaves. It's very hard to drop someone else into an unfamiliar codebase and have them pick up where the original person left off, and you probably would've made many different decisions (about product, platform, languages, architecture) with a different team.
The real fail there is poor relationship management. Why did the cofounder quit? What was running through their head? Did they not really want to commit to a startup in the first place, in which case the business founder should've vetted them more thoroughly before starting the company? Or did they lose trust in the business founder's leadership, market knowledge, and integrity? Were their incentives never aligned to begin with?
Maybe the tech cofounder quit because you're a clueless asshole? Blaming your failure on the guy you drove away, I think that's what he's complaining about as delusional.
> It's very hard to drop someone else into an unfamiliar codebase and have them pick up where the original person left off,
Eh, this is what every new employee at an established company does.
And when a startup has a "technical cofounder", that usually means the "tech" is a CRUD website, as opposed to a novel invention being productized (in which case it would be a technical founder or technical founder pair.
I've been involved in a start-up where the technical co-founder did some pretty bad stuff and ended up leaving the company. They survived, but it wasn't pretty.
Heh, yeah I would advise if you're the "find funding" type of serial entrepreneur to think long and hard about what you write there. It may come back to bite you.
It is also true of those who do have well reasoned arguments as to why they failed. They could be totally wrong, there are just so many internal and external factors that influence a business.
My top at-a-glance eye-roller says "technical co-founder quit & pulled the code out from under me".
So completely neglectful of basic business structuring that the tech co-founder could just walk away with the code, to which you don't have copyright claim? If a non-technical co-founder can't even bring responsible management to the table, why are they at the table?
Article goes on to suggest that if the non-technical co-founder had learned to code so as to not feel so helpless, things would have gone better. Just wow.