014: We should contribute more to open source

12/23/22 • 18 min

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!

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!

Previous Episode

013: Go's concurrency to the rescue

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.

Next Episode

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