I have started my startup at 30 when I was engaged (now married).
Every path is different but I think there are a couple of guidelines that I recommend:
- Talk with your partner and set expectations from the beginning. Please do not romanticise the journey - it's damn hard and full of sacrifices. Others have suggested a deadline - I also did that but find it a bit unrealistic because you'll have excuses to continue devoting an unhealthy amount of time to your company. Be kind to your partner and acknowledge that they will take more load in family duties and you'll have less time to spend with them.
- Find a co-founder that is complementary to you and that you trust. Being a solo founder in your 30s with a family is super hardcore even if you already have found product market fit.
- Do not invest your own money. Finding an early champion of your project and your founder team that could be an angel investor to kickstart things is a must. The alternative is to do it as a side gig until you can reach some kind of Ramen profitability scenario - I'm not a big fan of this because you'll likely focus on revenue too early on.
Happy to chat about my experience if you think it'll be valuable (just DM)
For me, the excitement comes from Microsoft spending big money on this tech. For those in the field of program synthesis it will be interesting to compare performance and viability of the tech. It's still early stages but this has been long coming and will put the emphasis of software development into more collaborative aspects such as architecture, design and code reviews.
I didn't mean about the costs for large OS projects but on the requirements. As an example, in my experience, I couldn't build the `semantic` project (https://github.com/github/semantic) with those requirements.
I also find the ability to process the logs with some other platform like Kibana to be a top feature; I suppose there will be apps on top of this soon enough to meet the demand.
I'm not sure if for large open source projects, these machines will be nearly enough to run the CI jobs.
The price for Linux seems quite steep when you compare with for example what you pay with GCP.
It will be interesting to see the Github security teams catching those "public" repos doing nasty stuff like mining crypto - even with hard timeouts on each job it will be cool to see how this plays out!