
Sign up to save your podcasts
Or


My desire to run a sustainable software business started somewhere near 2003 in the Business of Software forum. I've built, sold, and acquired a dozen of products since that time, with I have to admit the majority of failures.
I've seen three distincts era for software companies, we're definitably in the 3rd one, one that still has to be identified as good or bad.
Software companies, especially calm company is excruciably hard to be successful at. But when you're honest and define what is success to you and set out realistic goals, there's ways to succeed even without have $2m in ARR.
Go is of course a great choice to build a SaaS, but software product has almost zero to do with technology, especially at first and you'll most certainly end up rewriting to a v2 at some point after learning what the product really need to be. So the good old advice of use what you're most proficent in to write code is most often than not the correct answer.
I talk about my experiences trying to run a sustainable software company for the last 17 years.
Links:
As always if you can talk about the show it helps spread the words. If you'd like to talk about something you're passionate about related to Go please reach out. If you'd like to support the show you can purchase my courses and/or take a Patron subscription.
By Dominic St-Pierre3.8
66 ratings
My desire to run a sustainable software business started somewhere near 2003 in the Business of Software forum. I've built, sold, and acquired a dozen of products since that time, with I have to admit the majority of failures.
I've seen three distincts era for software companies, we're definitably in the 3rd one, one that still has to be identified as good or bad.
Software companies, especially calm company is excruciably hard to be successful at. But when you're honest and define what is success to you and set out realistic goals, there's ways to succeed even without have $2m in ARR.
Go is of course a great choice to build a SaaS, but software product has almost zero to do with technology, especially at first and you'll most certainly end up rewriting to a v2 at some point after learning what the product really need to be. So the good old advice of use what you're most proficent in to write code is most often than not the correct answer.
I talk about my experiences trying to run a sustainable software company for the last 17 years.
Links:
As always if you can talk about the show it helps spread the words. If you'd like to talk about something you're passionate about related to Go please reach out. If you'd like to support the show you can purchase my courses and/or take a Patron subscription.

273 Listeners

384 Listeners

290 Listeners

623 Listeners

153 Listeners

586 Listeners

284 Listeners

984 Listeners

189 Listeners

181 Listeners

62 Listeners

140 Listeners

59 Listeners

16 Listeners

65 Listeners