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 ToolPop — Screen sharing for remote teamsIf 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.
--------
1:03:05
--------
1:03:05
065: We're in the 3rd age of SaaS
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.
--------
49:10
--------
49:10
064: Podman, the root-less alternative to Docker
I retried Podman to replace a production service and did not wanted to re-installed Docker, mainly for security reasons. The fact that podman runs containers on the user-level and completely isolated from the system is a great alternative to the Docker deamon.I'm trying something new for this episode, I'll try and get audio clips from people to add more dynamism to the episodes, if you can join the Slack channel and also I've started a Patreon if you want to chip in and help me keep the mic on.Links:My new course Zero to Gopher (50% off for listeners)Blog post to view commands and the back storyBuild SaaS apps in GoBuild a Google Analytics in GoPlease talk about the podcast, share the episode, join the slack channel. Purchasing my courses and Patron are great way to monetary support the show.
--------
31:46
--------
31:46
063: Common mistakes when testing with Jakub Jarosz
Jakub is returning to the show, he's about to launch a book called "50 Go Testing Mistakes" and we talk about the most common mistakes Gophers are making when it testing. Having a trustable testing suite is known to be critical for long-live software system. I can testify having maintained a .NET codebase for 20 years without any tests, it sucks.Links:Jakub's websiteMailing listLinkedInBluesky
--------
57:55
--------
57:55
062: Your Go linters don't know how to fix your code
One university published attracted my attention, because it was on Go, it's titled: "Assessing Golang Static Analysis Tools on Real-World Issues".Do you find your static analysis and linters tools could be more helpful when reporting issues?I'm mixed feeling really, I think that they're pretty damn good. Tools can always improve for sure, not sure if we will need the help of LLMs to mix static analysis checks and LLM analysis / proposed fixes, maybe that will be the next step for those tools.Links:Paper's link
México