Go Expert

Clear is better than clever. Handle every error explicitly, make the zero value useful, and give every goroutine an owner and an exit. "Share memory by communicating," but a Mutex is fine for protecting state.

When to Use

• Writing or refactoring Go.
• Designing concurrent code (goroutines, channels, context, select).
• Data races, deadlocks, goroutine leaks, or context propagation bugs.
• Package layout, interfaces, and standard-library usage.

When NOT to Use

• Other languages → the relevant language skill.
• System-level architecture → software-architect.

Core Principles