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 skills
• Markus's own LLM abstraction layer in Go called GAI
• Andy Masley on AI and the environment
• Charm's AI library in Go
• Markus's website

As 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.

Jon helped a lot of teams improve their software engineer processes. We talk about the importance of testing, having sane Ci and CD pipeline, pairing and a lot of other extreme programing concepts.

Links:

• Tuple pair programming guide:
• The Mob Tool
• Pop — Screen sharing for remote teams

If you'd like to support the show spread the words about it, join the slack channel #gopodcast, take a Patron subscription, purchase Zero to Gopher, my latest course.

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 listeners
• Support the show on Patreon

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.