All Episodes

Displaying episodes 1 - 30 of 40 in total

040: CLI in Go and other tech talks with Marian Montagnino

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

039: Go is now more fun to build web apps

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

038: Finally, found a good use case for Go's plugin

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

037: Is Go a good choice for your Startup?

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

036: Game UI in Go with EbitenUI maintainer Mark Carpenter

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

035: Going deeper into Encore with its founder André Eriksson

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

034: Encore, domain design in Go with Bill Kennedy

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

033: Deployment orchestrator in Go, part of my upcoming SaaS

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

032: Go cryptography with John Arundel

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

031: Using shim on API to prevent breaking changes

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

030: gRPC in Go with Chris Shepherd

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

029: I've a confession to make, I've wrote 2 apps in Django

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

028: To TDD or not... or when

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

027: Debugging in Go with Matt Boyle

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

026: We can do better with interviews and onboarding

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

025: Iterators are coming to Go

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

024: Do you understand this weird production behavior?

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

023: Reaction to reddit post on null pointer error in Go

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

022: What to answer to "Why Go?"

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

021: Why I had to work 30h straight in 2002

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

020: Discipline is required to build long-live software

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

019: Dependencies maintenance in Go

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

018: WebAssembly runner, a real-world use case

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

Help your OSS with GitHub CLI, Codespaces and linters

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

016: What I'd hope WASM brought to web dev

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

015: How do you put things in production?

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

014: We should contribute more to open source

An ode to open source. I believe we should try to help more the projects & libraries we're using to build our software. Maintaining and contributing to open source pro...

013: Go's concurrency to the rescue

Real-world story about how Go's concurrency save a .NET performance issue I was having where I needed to call a process that takes 5 to 15 seconds to complete 6m times.

012: Concurrency isn't Go main selling point

Concurrency is hard, building concurrent systems is difficult. I don't think the major selling point of Go is its concurrency model. When trying to have a team adopt G...

011: Options where to deploy your Go servers

I talk about the three main options to deploy your Go web API. From managing your own server to PaaS to function-as-a-service.

Broadcast by