Goroutine leaks pass every test until prod runs out of memory. Wire goleak into TestMain and read the stack back to the guilty go func().
Book: The Complete Guide to Go Programming
Also by me: Hexagonal Architecture in Go — the companion book in the Thinking in Go series
My project: Hermes IDE | GitHub — an IDE for developers who ship with Claude Code and other AI coding tools
Me: xgabriel.com | GitHub
You've seen the graph. A Go service that idles at 40 goroutines
Stop printf-debugging Go. Learn Delve breakpoints, conditional breakpoints, goroutine inspection, and attaching to a live process.
A senior backend engineer's field notes on lock contention, goroutine leaks, semaphores, pprof, and production-grade Go…
Cache stampedes flood your database with duplicate work. Go's singleflight collapses concurrent calls into one, with a…
This is Part 2 of my series building Loom. 👉 Missed Part 1? Read it here Today: Reflection cache,...
The Go proverb in practice: when a channel that transfers ownership beats a mutex that guards state, and how to pick per…
Consumer-defined interfaces keep Go surfaces small, fakes trivial, and import cycles gone. The rule most Java-shaped Go code…
