Google Go Style Guide

Official Google Go coding standards for idiomatic, maintainable code.

Golden Rules

1. Run gofmt before commit — formatting is non-negotiable
2. Short variable names in small scopes — i, err, ctx
3. Error handling, not exceptions — check every error
4. Interfaces for abstraction — accept interfaces, return structs
5. Defer for cleanup — ensure resources are released
6. Explicit is better — avoid magic, prefer clarity
7. Package names: lowercase, single word — no underscores

Quick Reference

Naming Conventions