go podcast(‪)‬ Dominic St-Pierre

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 GitHubEbitenUI documentationEbitenUI on RedditEbitenUI on DiscordAwesome EbitengineAs 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 - websiteEncore on GitHubAndré on TwitterHow 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 repoArdan Labs Encore GitHub repoArdan Labs Service GitHub repoBill on TwitterArdan LabsAs 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: CryptographySubscribe to John's contentJohn on TwitterAs 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.