I like the authors summary, "Simply put IfC offers the simplicity of fully managed platforms like Vercel, with the flexibility of do-it-yourself platforms like AWS." Certainly what I've heard from others who are benefiting from IfC as well.
Congrats on what you've built so far. I'm curious if you have ideas or plans on how to gauge and communicate demand for experts for an open source project you don't have listed yet. It would be cool as a project contributor to know where unmet expert needs are in the community.
So we are logging requests and will reach out manually. Not today, given the Hacker News traffic load! But we are intending to put in a more scalable solution - what we don't want to do is spam people, which would be the result if it were fully automated.
I definitely agree with the advice to seek therapy for the inevitable relationship issues over coaching. Coaches definitely will help the individual but the experience is typically so one sided that it can often result in making tensions worse. A co-founder leaving can cause a lot of trauma to organization that is impossible once one leaves. I'm sure founders think the main impact is individual but let's be honest, it affects the entire staff. So yeah, co-founder tension needs to be treated like a marriage for the benefit of the co-founders and especially the benefit of the employees.
On the other hand I think it's important for leaving to be normalized and accepted as an option.
In my previous startup there were an increasing number of irreconcilable differences between me and my then-cofounder's style of working, management, and doing business, and though we had tried a lot I don't think me being egged on by everyone in the system to stay in the company while depressed about it was helpful.
The reality is cofounders can leave (legally) and we already have a perfectly good structure (vesting schedule) to deal with such decisions fairly, we just need to normalize it actually happening when it needs to happen.
