All Episodes
Displaying episodes 31 - 42 of 42 in total
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.
010: internal package gotchas
I talk about how the internal package can be used wrongly. I recently had to expose a Go package that I never thought would be expose, hence I've heavily used the inte...
009: Set variables at build time with -LDFLAGS
I talk about how I'm using the -LDFLAGS to inject variables value at build time so it's easier to grab the exact Git commit hash that user are using when reporting iss...
008: The day my Go service got csharpify
I talk about a personal experience where a Go micro-service got csharpify via OOP design pattern and why I think C# / Java developers should approach Go with a much si...
007: Is Go's database/sql verbosity that bad?
I go over some choices and scenarios Go programmers have regarding options to talk to databases.
006: Build softwares that stand the test of time
I gave 3 reasons why I think Go is one of the best language to build long-live programs. Programs that need to run for 15-20+ years.
005: Spring arriving, so is Go 1.18 and Generics
Is Generics going to cause a fragmentation in the community? What's the big deal about it, I personally will appreciate less for-loop where it make sense to reduce ver...
004: Using interfaces for major refactor
I talked about a major refactor I did with StaticBackend adding PostgreSQL support into a tightly coupled MongoDB code base using interface to clean everything up.
003: Pointers or !Pointers, stack, and heap
What are pointers. When not to use pointers and are pointers an optimization vs. using variables.
002: Project structure & package name
I talked about project structure and why it's intimidating at first, coming from other languages with established structure & frameworks. However, it's OK not to have ...
001: Error handling in Go
I talk about error handling in Go, why I think it's good but after a little bit of time getting used to have error as values.