Book: The Complete Guide to Go Programming Also by me: Thinking in Go (2-book series) — Complete Guide to Go Programming + Hexagonal Architecture in Go My project: Hermes IDE | GitHub — an IDE for developers who ship with Claude Code and other AI coding tools Me: xgabriel.com | GitHub A new hire on a Go team opens a PR. Title: "Pool everything." The diff wraps every short-lived struct allocation in a sync.Pool Get/Put. The benchmark in the PR description shows a small win on one endpoint. Other endpoints regress. None of it is caught in review, because the pooled-everything code looks like exactly the kind of thing senior reviewers skim past. That is the sync.Pool story in most Go codebases. Someone reads a blog post about how bytes.Buffer reuse cut allocation pressure for fmt , decides allocation is the enemy, and starts pooling things that should never have been pooled. The result is code that is harder to read and slower than the version it replaced. sync.Pool is a useful primitive.…