Coding Style

Core philosophy

Write simple, easy-to-read, self-explanatory code. Do not try to be clever or do too much in one place. If a simpler version of the same code exists, write the simpler version.

This applies especially to Go — Go code should look boring. If a function needs a paragraph to explain what it's doing, it's probably doing too much.

Language conventions

• Follow idiomatic Go patterns strictly: standard naming (short receiver names, err for errors, no stutter like pkg.PkgThing), standard project layout, standard formatting (gofmt/goimports).
• Prefer the standard library first. Do not add a third-party dependency unless explicitly asked to.
• Explicit error returns everywhere — never panic for expected/recoverable failures. if err != nil { return fmt.Errorf(...) }, not panic(err).

Naming conventions