go
January
- 04
- Keep track of environment variables in go
- 17
- REST Servers in Go: Part 1 - standard library
- 19
- Non-Blocking Parallelism for Services in Go
- 21
- A Tour of Go 1.16's io/fs package
- 23
- Command PATH security in Go
- 30
- Demo on creating worker pool in GoLang
February
March
- 06
- Go modules considered harmful
- 07
- Why We Switched from Python to Go
- 16
- Rust vs. Go: Why They’re Better Together
- 22
- Darker Corners of Go
- 30
- Know Your Nil
April
- 03
- Go HTTPS servers with TLS
- 07
- A practical guide on calling Go from Python using ctypes
- 24
- Writing Good Unit Tests; Don’t Mock Database Connections
May
- 03
- The art of solving problems with Monte Carlo simulations
- 11
- pprof++: A Go Profiler with Hardware Performance Monitoring
- 12
- Interfaces and Nil in Go, or, Don't Lie to Computers
- 13
- Half a million lines of Go
- 24
- Discovering goroutine leaks with Semgrep
- 27
- Functional programming in Go with generics
- 27
- Why Go Getting Generics Will Not Change Idiomatic Go
June
July
August
- 12
- Common Anti-Patterns in Go Web Applications
- 28
- Plugins in Go
- 29
- Develop a Go app with Docker Compose
- 30
- Go is pass-by-value — but it might not always feel like it
September
- 11
- I18n in Go: Managing Translations
- 15
- Go'ing Insane Part One: Endless Error Handling
- 22
- Taming Go’s Memory Usage
- 25
- Go and JSON: Tags, Empty Strings and Nil Values
October
November
- 05
- Hypocritical Gophers
- 06
- Reducing Memory Allocations in Golang
- 09
- Upcoming Features in Go 1.18
- 10
- Twelve Years of Go
- 21
- AWKGo, an AWK-to-Go compiler
- 22
- Writing an application using Go and PostgreSQL
- 26
- Go Does Not Need a Java Style GC