Explorez tous les épisodes du podcast go podcast()

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 story
• Build SaaS apps in Go
• Build a Google Analytics in Go

Please talk about the podcast, share the episode, join the slack channel. Purchasing my courses and Patron are great way to monetary support the show.

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 website
• Mailing list
• LinkedIn
• Bluesky

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

I finally gave Gleam a serious look and ho boy I'm excited. I've looked at Gleam a long time ago back when it started with the ML-like syntax. I've always been an Elm fan, I discovered functional programming with Elm. Near 2016-2017 I tried Elixir and Phoenix, and gave it a try multiple times following the years, but I'm not fully sure why it never clicked completely for me.
As someone engage with Go for the last 10+ years, I won't lie that I was looking for some excitement lately. Not because I'm tired of Go or anything, I've dabbled seriously into Python/Django in the last 3-4 years. But Gleam, at least so far, as this I don't know what that I felt when I started Go back in 2014.
There's so many programming languages these days that I suppose it's really comes down to a matter of taste. I do have some minimal checkboxes that a language must checked before I even considered looking at it, and Gleam was checking them all. It's a refreshing language after 10 years of Go. Just another tool in the toolbox, but I'm extremely picky about which tool I put in my toolbox haha, so Gleam for now is in the evaluation phase, but so far I'm excited and I haven't felt like this for a long time.

The message is everywhere: LLMs are here to make us 10x more productive and change software development forever. Venture capitalists are pouring billions into the vision, and big tech companies are pushing hard for us to adopt the tools. But as a software engineer who’s seen the demos and lived the reality, something feels profoundly wrong.

This week, I’m taking a step back to reflect on the current state of our industry. We'll explore the inconvenient truth that often gets lost in the hype: that relying on AI can sometimes make us slower, introduce more technical debt, and even erode the fundamental skills that make us valuable.

But maybe the real problem isn't the technology itself. Maybe it's that we're looking for a quick fix for a deeper issue. Join me as we discuss what really drives developer productivity, the crucial importance of domain knowledge, and whether anyone is even considering the quality of life for the people building our systems.

Because while the "going from 0 to 1" demo is impressive, our jobs are about maintaining complex systems from 1 to 1000. And maybe, just maybe, an agentic flow that doesn't care about our codebase isn't the real solution we need.

p.s. And yes, I used LLM to improve my description draft ;)

Let's talk with a friend of the pod, John Arundel. We talk about state of thing a little regarding Go's maturity, a bit of AI, I personally am a bit fatigue of the noise and "agent". The podcast is returning slowly. , John has written a new Go book that's beginner-friendly, but goes deeper than you'd expect, he produce excellent learning and training resources.

Links:

• The Deeper Love of Go
  • John's newsletter

Go is used by multiple programmers and software engineers. Lots of path can lead to want to try Go, and this week I talk with Yann whom eventually found Go and talks about his experiences writing internal tools at his company.

Links:

• Hupload
  • YBFeed

The part 2 of my talk with Ivan Fetch. We cover the remaining listener questions and go over some aspects in more details of being blind in tech.

This week I'm joined by Ivan Fetch. We talk about challenges and day-to-day life as tech professionals being blind, using a screen reader. This is the part one as we've a lot to cover. Since I started this pod after telling guests I'm blind and use a screen reader everyone wants to know more, so I thought doing an episode would be interesting to people wanting to know more.

The best way to support the show is by talking about it and sharing the episodes. If you can you can buy my courses which help keeping the lights on for the efforts invested to bring the pod, there's a 50% off discount for listeners of this show: Build a SaaS app in Go and Build a Google Analytics in Go.

This week I'm joined by Tristan Mayo, the creator of Zog, a Go library that helps with validation when receiving data from an HTTP POST or parsing data. 

Links:

• Zog on GitHub

This week I talk with Delaney Gillilan, the creator of Datastar, a framework that helps building web applications with the reactivity of a single page app but with the programming model of a good old server-rendered page from the backend. Datastar combines the power of HTMX and Alpine.js in a simple and lightweight way.

Links:

• Datastar website

The best way to support the show at this time is by talking about the pod and if you can, purchase my courses, which are at 50% discount for listeners of the show: Build SaaS apps in Go and Build a Google Analytics in Go.

Markus is back to talk about Gomponent. I've used the library in production and wanted to tell the story of my experience converting my html/template to Gomponent and get his thoughts and reactions. This is more of a real-world episode than anything else, a real story of real usage of Gomponent.

Links:

• Gomponent

As always the best way to help is by sharing and talking about the show. If you can you may contribute by purchasing my courses, this helps with all the efforts and costs of running a podcast, courses are at 50% off: Build SaaS apps in Go and Build a Google Analytics in Go.

This week I'm joined by Peter Strøiman, the author of Gost, a Go headless browser that can be pretty useful when doing TDD and even (especially) if you're using HTMX. We talk about the challenges and the "why" Peter wanted to build this project, where it can be helpful and we dive into the internals a bit.

Links:

• Gost on GitHub
• Peter's website

As always I'd appreciate if you can talk about the pod and if you can and want to support to cover cost the best way is to purchase my courses which are 50% off for listeners of the show: Build SaaS apps in Go and Build a Google Analytics in Go.

This week I'm joined by Morgan Hallgren and we talk about Event Sourcing. Morgan created an open source library that helps with the parts involved when doing event sourcing.

Links:

• eventsourcing library (GitHub)

As always the best way to support the show is by talking about it. If you'd want to chip in as it's time consuming and costly to host a podcast, the best way is to purchase my courses which listeners get 50% off: Build SaaS apps in Go and Build a Google Analytics in Go.

This week I'm joined by Jakub Jarosz and we talk about security, devops, testing a lot of topics that are fun and comfortable doing in Go.

Links:

• Jakub on Bluesky
• Jakub's website

As always I'd appreciate any mention about the podcast and reach out if you'd like to join as a guest. If you'd want to support the show you can purchase my courses at 50% off Build SaaS apps in Go and Build a Google Analytics in Go.

go podcast() is back. After debating about canceling or continuing the pod, I've took 2 months and decided to resume publishing episode. I'm looking at a formula for the 4th year of the podcast. I'll still do interviews with Gophers as much as I can. But to fill the gap, I'd like to have something special, maybe more story based that would allow me to publish regularely, like each week.

In this episode I talk mostly about how innevitably my integrations and e2e tests sucks and are borderline untrustable after sometimes.

If you'd like to record an episode as a guest reach out, these days I'm on BlueSky as @dominicstpierre.com

As always you can support the show by talking about it, sharing the links. You may also purchase my courses at 50% off: Build SaaS apps in Go and Build a Google Analytics in Go

I'm receiving Lea, creator of the Wails project. Allowing Gophers to build desktop application using web tech for the frontend.

Links:

• Wails.io

Want to support me with the show, talk about it and rate it where you're listening. Also you can purchase my courses at 50% off for listeners of the show: Build SaaS apps in Go and Build a Google Analytics in Go.

This week I talk with Andy Williams about the Fyne toolkit. It's impressive how much you can do with Fyne targeting mostly all platform where you'd want your application to run. In a world where web is getting a little bit out of hand, it's refreshing to see that desktop still have its place in the software world.

Links:

• Fyne website

Join us on #gopodcast in the Gophers Slack. Any mention of this podcast would be extremely appreciated. To support the effort of running the pod you can purchase my courses at 50% off for listeners: Build SaaS apps in Go and Build a Google Analytics in Go.

John is proposing learning Rust to enhance Gophers programming knowledge. I do enjoy learning new thing personally, Rust always has been or at least seems to required an extra effort to get started with. John is trying to make it more approachable.

Links:

• John's website
• The secrets of Rust, Tools
• John on Twitter

If you enjoy the show the best way to support it is by sharing and talking about it to your circle and if you can by purchasing my courses (50% off for listeners of this show). Build SaaS apps in Go and Build a Google Analytics in Go.

This week I'm joined by Markus Wustenberg, the author of Gomponent, a library that lets you write your HTML directly in Go using a component approach with type safety.

Links:

• Gomponent main website
• Markus's blog
• Markus's Go course

There's a channel in the Gophers slack community, join #gopodcast.

If you'd want to support the show consider purchasing my Go courses, which are 50% off for listeners of this show. Build SaaS apps in Go and Build a Google Analytics in Go.

After last episode with Templ maintainers I was really pumped to try Templ and see if it would work for me. Without spoiling too much I believe it would have been easier to start from scratch with Templ vs. trying to migrate an existing project.

This led me to try and see if I could add static analysis of my templates in my library tpl. I don't really have a PoC yet, but kind of getting close to it. If everything continue I should be able to capture errors in using of wrong field in template, like typos in field name that are caught at runtime at this moment.

Links: https://github.com/dstpierre/tpl

Also if you want to support this show, this is a 50% discount on my courses: Build SaaS apps in Go and Build a Google Analytics in Go.

In this episode Adrian Hesketh and Joe Davidson from Templ joins me and we talk about the what, why, and how of Templ. If you haven't checked it out, Templ helps creating strongly typed html template and use a component based approach to building web interface in Go.

Links:

• Templ GitHub repo
• The documentation
• Go ship it
• Quicktemplate

As always if you want to support the time I invest into this podcast the best way is by purchasing my courses which are at 50% off for listener of this pod: Build SaaS apps in Go and Build a Google Analytics in Go.

Ramesh joins me this week to talk about his experiences teaching programming in Girls who code club and gate keeping that can discourage some people from choosing computer science as their career path.

Links:

• Confluence podcast with Ramesh
• Scott Hanselman's blog Profanity doesn't work
• Ramesh's blog
• Hanselminutes podcast
• ChangeLog

I'd appreciate any mention you can share about the pod. If you'd like to support the effort, the best way if to purchase my courses, listeners of the show get 50% off Build SaaS apps in Go and Build a Google Analytics in Go.

Getting out there, showing what you're currently doing / learning, starting a blog, creating content to help other software engineers, those are all good way to distinguish yourself. You might want to consider speaking at conferences as well. In this episode we're talking with Matt Boyle about the what, why, how of getting your first conference talk accepted.

Links:

• @GopherCon on Twitter
• Sessionized
• Matt's blog post on what should you build
• Writing a successful GopherCon proposal
• ByteSizeGo Matt's courses and books

As always I'd appreciate if you can talk about the pod, share a link, add a review. If you want to support the efforts the best way is to purchase my courses: Build SaaS apps in Go and Build a Google Analytics in Go.

I'm joined by Marian Montagnino this week. We talk about CLI in Go, programming languages. Java and Elm mentioned, be warned .;) and other tech related stuff. Marian wrote a book on building CLI in Go and presented multiple talks at Go conferences.

We had some connectivity glitches during our call making it challenging. You won't here the internet cuts as we did, but the lag is real, sorry about that.

Links:

• Building Modern CLI Applications in Go
• Marian on Twitter

As always I'd highly appreciate any mention of the pod and if you want to support the show the best way is to grab my courses at 50% off for listeners of the show: Build SaaS apps in Go and Build a Google Analytics in Go

I started a monolith-style web application couple of weeks ago and force to admit that Go is more and more fun to use where I was considering more like Django or Rails before.

For me there was still the templates aspect that needed to be fixed, and I wrote a library for that. The other major place where I was not enjoying myself was the database code, found it way to repetitive for application that had a lot of SQL tables.

We're in a very good place at the moment and the benefits of having a compiled language to build heavy backend web application is great.

Links:

• dstpierre/tpl - a simple library to help with templates structuring, parsing, and rendering
• sqlc - I finally surrender, and I like it

As always if you want to support the show you may purchase my courses Build SaaS apps in Go and Build a Google Analytics in Go.

I've restarted active development on my open source Go backend server API StaticBackend. For a long time I wanted to make its CLI size smaller, and I decided to use Go's plugin package to extract a functionality that used a dependency that was accounting for more than 50% of its 170 MB. Go plugin were the solution I decided to use for this and I explain the problem and the solution in this episode.

Links:

• StaticBackend on GitHub
• go-size-analyzer

As always it's appreciated if you can talk about the pod and share. You may also purchase my course(s) if you want to contribute with money, there's a 50% off coupon with those links: Build SaaS apps in Go and Build a Google Analytics in Go.

As always 

I've been building SaaS since 2008 and built two with Go. Big spoiler, the technology you choose has a little impact in the early stage of a software business. There's some danger to over-engineer and use complex construct while you still does not even know if what you're building is desirable. Heck, you don't even know what you're building at first.

I'm giving some example of common traps and pitfails technical founder tend to fail into when jumping into a startup venture for first times. And yes, times is plural, because it takes multiple attempt before learning lessons.

If you enjoy the pod please consider sharing / talking about it. You may also contribute by purchasing my courses Build SaaS apps in Go and Build a Google Analytics in Go courses, they're at 50% off for listeners of the show.

I'm joined by Mark Carpenter, the maintainer of EbitenUI, a UI library you may use with your Ebitengine Go game. Game dev is slowly making its way to Go with game library like Ebitengine and Raylib. The nice thing about Ebitengine is that it's built in Go, have great cadance in its development and is simple to use.

EbitenUI is a UI library that allows you to build UI for your games. It's a simple library that integrates smoothly with the programming model of Ebitengine games.

Links:

• EbitenUI on GitHub
• EbitenUI documentation
• EbitenUI on Reddit
• EbitenUI on Discord
• Awesome Ebitengine

As always if you want to support my efforts with this show please talk about it, share it. You may also purchase my online courses Build SaaS apps in Go and Build a Google Analytics in Go, there's a 50% discount for listeners of this show.

A follow-up episode on last week episode. We go a little bit deeper into Encore with André Eriksson. Encore can do a lot for your Go project and infrastructure. It allows your team to focus on your product and provides local development and DevOps tooling that help your team go faster.

Links:

• Encore.dev - website
• Encore on GitHub
• André on Twitter

How to support the show:

• Share and talk about it.
• Purchase my courses: Build SaaS apps in Go and Build a Google Analytics in Go (50% off for listeners of the show).
• Want to join as a guest, pitch me your idea via Twitter @dominicstpierre.

This week I'm joined by Bill Kennedy. Bill makes me discover Encore which can handles service-to-service communication while programmers focus on their application. We talk about domain design in Go and how to architect an isolated system following the 3-tier layer design.

Links:

• Encore GitHub repo
• Ardan Labs Encore GitHub repo
• Ardan Labs Service GitHub repo
• Bill on Twitter
• Ardan Labs

As always if you enjoy the show consider sharing it / talking about it. If you'd want to support the effort the best way is by purchasing my courses, Build SaaS apps in Go and Build a Google Analytics in Go. Those links have a 50% discount coupon applied to them for listeners of the show.

My upcoming SaaS product at first wasn't suppose to be rolled out as a product, but was for my own usage. Turns out as I was using it and selling my online courses that it appears to me as being fairly usefull and could compete against existing course selling platform.

The hic is that it wasn't built as a SaaS in mind, so I have to deploy one application per customer. It's completely multi-tenant. To help with automating the deployment of a new tenant, I wrote and orchestrator with agents to facilitate the deployment of a new application. I thought this part could be interesting to hear about as it's written in Go.

Want to support the show? The best way is by purchasing my courses Build SaaS apps in Go and Build a Google Analytics in Go. Listeners of this show get a 50% discount on all store product.

In this episode I talk with John Arundel about cryptography in Go. John wrote a great book on the subject called Explore Go: Cryptography.

Security is a growing concerns and you should up your game as a Go programmer. We're lucky to have such a solid crypt package in the standard library. I'd encourage you to get familiar with it if you haven't yet.

Links:

• Explore Go: Cryptography
• Subscribe to John's content
• John on Twitter

As always, if you want to support this show the best way (other than talking about it) is by purchasing my courses: Build SaaS apps in Go and Build a Google Analytics in Go, here's a 50% direct discount for listeners of this podcast.

In 2021 Twilio sent a termination email on their Fax services. I was consulting as the CTO in a credit bureau that was in the start of an acquisition process with Equifax Canada. There was just no time to "waste" on changing provider and rewriting this part of the system to satisfy the new provider API.

Would have been grand if the provider would have offered a shim that replicated Twilio's API and map that to their own API. Imagine how many companies needed to rewrite this part at the same time. Offering this as the provider that receives X thousands new customers would have been a superb engineering experience.

So maybe we can apply this concept internally as well. When a team needs to introduce breaking changes, a good solution might be for them to provide a shim over the old API so no other teams need to do anything.

This is obviously a tad dangerous and might introduce some technical debt. But as everything, it depends.

I receive Chris Shepherd and we talk about gRPC in Go. If you're building systems with lots of micro-services, gRPC is a good way to provide strong contracts between your services and improve communications.

Links:

• Chris on Twitter
• The Buf CLI
• Example protobuf registry

The best way to support this show, other than talking about it, is by purchasing my online courses on Go: Build SaaS apps in Go and Build a Google Analytics in Go. Here's a direct link with a special discount for the pod listeners.

This episode was supposed to be focussing on templ, the tempalte library, but as I was going in details I found it hard not to explain the back story of why I started looking for something to help html/template be more "fun" to build rapid side projects, you know, CRUD heavy web application.

Links:

• templ: https://templ.guide/
• The lib I forgot the name during the episode: https://github.com/Masterminds/sprig

If you'd like to support this show the best way is to puchase my courses, I've one call Build SaaS apps in Go and another one called Build a Google Analytics in Go. Here's a direct discount for listener of this show.

Quick solo episode on TDD and when I experienced it was used best and when I personally not use it but use an approach of writing a bit of code, than tests, thant another bit of code, etc.

Buying my courses is the way to support this show, here's a direct discount for listeners.

I chatted with Matt Boyle about debugging Go code. Matt is creating a course about this topic and discussing debugging as a tool you may add to your toolbelt.

Links

• The Ultimate Guide to Debugging With Go
• Domain-Driven Design with Golang
• Matt on Twitter aka X
• Goland Insiders (Go Twitter community)

As always, if you'd like to support this podcast the best way is to purchase my courses / talk about them. I have 2 courses on Go and here's a direct discount for podcast listeners.

I believe we can do better regarding software engineer interviews and this entire process (also including onboarding). I think companies that will be mediocre at those two aspects will have a hard time with younger programmers, which I fully support.

Iterators are going to be useful to process large amount of data without having to load an entire slice or maps in memory but instead create iterators that can be used from a for item := range myIterators().

If you'd like to support this show and/or are interested in Go courses I have, here's a direct discount link specially for listeners of this show.

Something absurd happened in 2024 for one of my consulting client's production web application, and this code for a time. The time zero value is behaving differently than it has been since 2018.

    Date has a value:     No date, zero value
I launched my new course Build a Google Analytics in Go, if you're interested and/or want to support this show that's how to do it.

I react to the post on the Go subreddit of last week talking about a null pointer error occuring in production for a Go program.

This is the YouTube video I made.

If you'd want to support this podcast, I have Go courses available for purchase here, I just launch my latest course Build a Google Analytics in Go with a 50% discount for listener of this show.

Typical reasons to use Go might sounds exciting for us used to Go, but might not be as attractive for people that haven't experienced Go yet and might not realize they have some small heritants that Go fixes/improves.

I've pre-launched my new course call Build a Google Analytics in Go, as listener to this podcast you're getting a 50% off during pre-sale, the course is due to launch before the end of December.

If you want to support this show, purchasing the course is the best way, also talking about it ;).

Things were very different when I started as a junior developer. This is a story of an out of the ordinary day where worked from ~9h am to 11am (the next day), the two of us that were in charge of everything at a small financial company.

This one has nothing to do with Go, but I thought it was worth telling as a story.

I'm soon to launch (pre-launch) my next course Build a Google Analytics in Go. If you're interested make sure to sign-up for the newsletter on my store. https://store.dominicstpierre.com/

As we're building more and more of distributed systems I believe that one trait / culture successful team will require is discipline. Personal opinion, we tend to complicate our lives in the last decade compare to what things were before. But without an extra attention to some details, it will be a nightmare to maintain systems in the long run.

As always, if you'd like to support the show the best way is to purchase my course. Sharing it also very much appreciated.

I talk about dependencies management in Go. How to keep your dependencies up-to-date and how to check if there's any updates available. What to do when a package change their major version.

List all packages and latest versions:
$ go list -m -u all

Update all packages to their latest minor versions:
$ go get -u ./...

If you'd like to support this podcast consider buying a copy of my course Build SaaS apps in Go.

I was toying with the idea of using WebAssembly runner as a plugin / extension mechanism from a Go (host) program to extend the capabilities of a program at runtime.

* min/max bult-ins coming in 1.21: https://tip.golang.org/ref/spec#Min_and_max
* wazero: https://github.com/tetratelabs/wazero
* wasmr: https://github.com/wasmerio/wasmer-go
* StaticBackend: https://github.com/staticbackendhq/core

I'm trying to make my open source backend API project StaticBackend as easy as possible to contribute.

Couple of things I've added lately was worth mentionning. GitHub Codespaces is helpful and nicely done. It goes 1-step further than Docker and make contributing to an open source project a simple task, especially for small and quick 1-time contribution.

This couple with GitHub CLI, which I admit, have just starting using it. And linters to make sure the quality of the code is as high as it can be.

StaticBackend website | GitHub repo

If you'd want to support this podcast, the best way is to talk about it, sponsor my open source project or purchase my course Build SaS apps in Go.

I talk about what I'd love to see coming to web development. While WebAssembly can be used as an alternative to JavaScript, I believe we're not looking into the real problems related to building web application.

It has been a rough last 4 months for me and I finally get a chance to restart publishing episodes. 

In this episode I talk a bit about what I've seen so far as process / flow for deploing software in production. Going from the old days when I started as a junior software dev where we were pushing straight into prod to what I discovered at a big organization where putting something in production spread accross multiple days and involves a lot of people.

I'd like to hear how things are working for you, what is your process from bug fix/new feature to production. I'm genuinely curious after the experience I had seeing how thins can be tedious for this process.