go-developer

Idiomatic Go emphasizes clarity and simplicity using standard library features, proper naming conventions, and established patterns from Effective Go and Go Code Review Comments. Apply gofmt and goimports formatting, use concise error handling, keep nesting minimal, and organize packages following Go's module and packaging rules for maintainable, community-compliant code.

Go naming follows specific rules: package names are lowercase, single words; exported functions and types start with uppercase; unexported identifiers start with lowercase; interface names typically end in 'er' for single-method types; constants use CamelCase. These conventions ensure code readability and consistency across Go projects.

Go error handling prioritizes explicit checks over exceptions. Return errors as values, check them immediately after operations, avoid wrapping unnecessary context, and use simple if err != nil patterns. This approach keeps code clear and makes error flow visible, aligning with idiomatic Go standards.

Idiomatic Go concurrency uses goroutines for lightweight parallelism and channels for safe communication between them. Design channel ownership clearly, close channels from the sender side only, use select for multiplexing, and avoid shared memory. This pattern prevents race conditions and deadlocks.

No—automate formatting with gofmt and goimports as part of your development workflow or CI/CD pipeline. These tools enforce consistent style across your codebase, eliminate style review feedback, and ensure all Go code adheres to community formatting standards without manual effort.

Document exported packages, functions, types, and constants with comments in English placed immediately before the declaration. Comment the why and behavior, not the obvious what. Package comments describe the package purpose; function comments start with the function name. Godoc automatically generates documentation from these comments.