How to Golang

Decision guide for Go development. Tells WHAT to use, not HOW. For HOW, read the library docs.

Principles

• Errors as values — no panics in library code
• Type safety first — make impossible states unrepresentable
• Composition over inheritance — always
• Generated over handwritten — sqlc, templ, govalid for boilerplate
• Observability built-in — OpenTelemetry from day one

Process

When working on a Go project: