Golang Design Patterns

This is the reference card you want open when building Go services at scale. It covers functional options (the right way to write constructors), graceful shutdown, resource lifecycle, retry patterns, and when to use strings vs byte slices. The persona pushes back on premature abstraction, which is refreshing. It assumes you already know Go syntax and focuses on the production patterns that separate a working service from one that leaks goroutines or hangs on deploy. Strong opinions on avoiding init() and starting enums at 1. Cross-references other skills in the same collection for error handling and context propagation, so it stays focused on architecture without retreading basics.