go podcast()

We're talking about multiple topics this week, which I'll let you discover because being total honest I forgot to wrote the title and description after we recorded, and now I'm late to post the episode haha and don't have time to listen back. One thing I do remember though is that we talked about datastar, HTMX, building web app in Go, databases, query optimization. Maybe the SpaceX stock came for a brief moment...

This week we talk about multiple in-the-news topics like the SalesForce announcement that Heroku is in ~maintenance mode and we surface the big observability topic as I'm preparing to implement something basic for StaticBackend and since Morten already have this in his open source project we duscuss about ways to add this after the fct and some parts of tracing your system.

We're trying something, each first episode of the month we'll talk about our respective open source projects. This episode will be more story driven than others, and you'll be able to follow our journey maintaining open source Go projects.Links:Andurel Morten's projectStaticBackend Dominic's project

I'm restarting this year after a small break, go podcast() turned 4 years which is crazy, although I'd have hope to have had a better consistency publishing episodes, it is what it is ;). I'm looking at bringing co-hosts from multiple background to add some diversity to the episodes, if you're intrigued please reach out.I've also decided to un-archived and restart working on StaticBackend, my Go open source backend-as-a-service project I started in 2019. I'm missing the pace of working on a problem, thinking about it for some time and implementing a solution while adding tests etc. I've recorded this episode twice because the first time I kind of sliped into a more dark / negative mood, and that's not what I want for the pod and not how I'm feeling about bringing StaticBackend back.Go's v1 "it will build" compatibility is underrated.Links:StaticBackend (GitHub)StaticBackend (website)Act run GitHub action locallyPlease if you can talk about the podcast it would help greatly. You can always purchase my Go courses, which are 50% off for listeners: Build SaaS apps in Go | Build a Google Analytics in Go | Zero to Gopher

This week I try to keep an open mind and we talk LLMs and AI with Markus Wüstenberg. Markus is a friend of the show and I noticed he was using a lot of LLM lately, I basically learn a lot by doing these podcast interviews, so I was interested to hear about what Markus is using LLM and AI in the systems he ships and also how does he uses AI as a software engineer in the day-to-day.Personally my experience so far is very mixed, sometimes it's good other it's pretty frustrating with LLMs either integrating functionalities augmented by LLMs or trying to integrate a coding agent in my day-to-day, let's just say that I'm not there yet. But I wanted to hear about someone that do have real production experiences using these things, and Markus gives a solid fundation to demistified some aspects, at least for me ;).Links:gomponents + Datastar:Markus's Claude Code skillsMarkus's own LLM abstraction layer in Go called GAIAndy Masley on AI and the environmentCharm's AI library in GoMarkus's websiteAs always if you're finding value in the pod talk about it, you may also purchase my courses, I launched Zero to Gopher 3 weeks ago, there's 50% off for listeners of the show.

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:My last course Zero to Gopher with a discount for listenersSupport the show on PatreonAs 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.