Go Logging

Opinionated, standard library first guidance for logging in Go. It pushes slog hard for new code, keeps messages static with structured key-value pairs, and hammers home the "log or return, not both" rule to stop error noise from cascading up the stack. The level semantics are sensible (Error means operator attention, not just "something went wrong"), and the request-scoped logger pattern via context is the right way to carry trace IDs through your handlers. If you're still using log.Printf or debating between zap and zerolog without profiling first, this will save you from yourself.