The Go error handling patterns I actually use in production: wrapping with %w, errors.Is and errors.As, sentinel errors, and errors.Join, with code.
Gin, Echo, Fiber, Chi, or plain net/http? I've shipped Go services on all of them. Here's the honest read on which one I reach for…
Go 1.21's log/slog brought structured logging into the standard library. Here's what it replaced for me, where it shines, and the one part I still…
Go 1.25 added WaitGroup.Go and a stable testing/synctest. Here are the Go concurrency patterns I actually use in 2026, and the boilerplate I deleted.
I've shipped production services in both Rust and Go. Here's the decision framework I actually use, with code, honest trade-offs, and no benchmark wars.
Four years into Go generics, here is what I actually reach for in production, the constraints I write, and the patterns I quietly stopped using.
I've used Go's range-over-func iterators in production for eight months. Here's what I keep reaching for, what I dropped, and where the new pattern bites.
I ignored Go 1.23 iterators for almost a year. Here's what finally made me reach for them, where they're worth it, and the footgun that…
I've shipped Go HTTP services with all the big frameworks. In 2026 I default to net/http with chi, reach for Gin to move fast, and…