go podcast()

At beginning I was deploying my Go servers to a DigitalOcean droplet. But for the last 3 years I'm enjoying Render, which listen to my git push and automatically deploy app for me in a blue-green deployment.

If you enjoy my podcast have a look at the following:

Build SaaS apps in Go, my course on building web application in Go
- StaticBackend, an open-source Go backend server API
- @dominicstpierre on Twitter

I recently created an exportable Go package from StaticBackend, an open source backend API which was self-hosted.

I ended up using the internal package way to heavily and this design decision bite me when I decided to create an exportable package. Now all things that needed to be expose that was in the internal package had to be refactored into their own packages.

Links:

• StaticBackend repo
• Go package

Don't stress too much about having the "proper" project structure to the point where you might over-engineer or be paralyzed by the thought of doing something wrong.

It's just hard, and even 5+ years of Go experience will not ensure you're creating the optimal packages and structure. It's an art mixed with preferences that become a little easier with time but remain challenging.

I wrote a getting started with Go guide that cover a little about project structure and how to get started with Go.

If you're in writing web applications and maybe even SaaS, I have a course on creating API-first SaaS with Go.

• Wrapping error: fmt.Errorf("error trying to do X: %w", err)
• Package errors: https://pkg.go.dev/errors

Example of not using the happy path at 1st indentation:

An example of happy path in idiomatic Go:

if !somethingElse() {
// handle something else false
}
// Happy path

My course on building SaaS apps 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.