Claim Ownershipgo podcast()
Subscribed: 25Played: 155
Subscribe
© 2023 Dominic St-Pierre
Description
15 minutes news, tips, and tricks on the Go programming language.
21 Episodes
Reverse
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 allUpdate 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 repoIf 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.
This is the last episode of 2022. Those are my thoughts about how I think we should try to help more as user of open source project and librairies.This episode content was inspired by the Gorilla Web Tool Kit archiving their Go projects.On that note, I'll be back with more Go content on January, and will try to keep my 1 episode per two weeks plan for 2023.Thank you!
Go's worker queue pattern:type WorderPool struct { queue chan int}func (wp *WorkerPool) start() { for i := 0; i < 500; i++ { go funcIO { for id := range wp.queue { doSomething(id) } }() }}func (wp *WorkerPool) add(id int) { wp.queue <- id}
Go 1.20 errors.Join / multiple unwrap error
My course: Build SaaS apps in Go
Best way to show support for the pod is by sharing it around and buying my course.
Let's talk about Go's concurrency. It's a powerful tool to have at your disposal but a hard one to master and use correctly.
The tweet that inspired this episode, I thought it was a recent one though...
Reach out on Twitter
Build SaaS apps in Go
If you want to support the pod the best way is to purchase my course (thanks).
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
Usage of -ldflags:go build -ldflags "-X main.varName=from_build" -o mycliInside your code:var varName stringfunc main() { fmt.Println(varName) // prints "from_build"}Here's what I'm using for StaticBackend -v flag:go build -ldflags \ "-X github.com/staticbackendhq/core/config.BuildTime=$(shell date +'%Y-%m-%d.%H:%M:%S') \-X github.com/staticbackendhq/core/config.CommitHash=$(shell git log --pretty=format:'%h' -n 1) \-X github.com/staticbackendhq/core/config.Version=$(shell git describe --tags)" \-o staticbackendLinks:
StaticBackend website
StaticBackend GitHub repo
Build SaaS apps in Go (my online course and book)
If you'd like to join the dev of StaticBackend a Firebase alternative I'm building in Go you're welcome, there's a discord if you'd want to chat. https://github.com/staticbackendhq/coreIf you'd like to checkout my course called Build SaaS apps in Go or want to support this show, that's the best way.If you're on Twitter make sure to follow me: https://twitter.com/dominicstpierre
sqlx: https://github.com/jmoiron/sqlxsqlboiler: https://github.com/volatiletech/sqlboilerIf you're looking to learn how to build web API with Go, checkout my course on building SaaS in Go.
I've been maintaining 20 years old systems for a long time now. I've been working with legacy applications in .NET. To me Go has some great advantages built-in by design that should help in 10-15 years from now when the applications that are created today will be on maintenance mode.
What are you thinking about Generics? What about 3rd party libraries that will pop from everywhere once Go 1.18 launched?Personally, I'll appreciate what the std lib offers and will wait before writing generics code, making sure I really need it.I'm currently working on a free and open-source self-hosted Firebase alternative - if such things sound interesting, please join the Discord group and contribution are very welcome (it's written in Go of course).This is my course on Building SaaS apps in Go.
If you'd like to check the code, the PR is still active.StaticBackend repo: https://github.com/staticbackendhq/coreMy course on Building SaaS in goShare episode topic idea with me on Twitter @dominicstpierre
We go over what are pointers and when to use or not use them. For instance, this is probably not a good use for pointers.func main() { var i int = 10 abc(&i)}func abc(i *int) { *i = 15}In my opinion any dereferencing is probably bad. Better way:func main() { var i int = 10 i = abc(i)}func abc(i int) int { return 15}I also try to give some basics info regarding the stack and heap and why pointers might not be seen as an optimization.I have a course on building SaaS in Go.Follow me on Twitter.
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.
Comments
Download from Google Play
Download from App Store
United States