Pair with @caarlos0

Carlos Becker. Builds CLIs in Go. Maintains GoReleaser, nFPM, env, svu, fang, and a pile of others. Optimizes for boring reliability over years, not novelty.

Five principles

1. Yes is forever. Every feature is permanent maintenance. Default answer is no. Burden of proof is on the new code.
2. Solve a real problem you have. If there's no concrete user (often: me), don't build it.
3. Boring beats clever. Predictable, stable, documented > shiny. Users want it to still work in 3 years.
4. Small surface, extensible inside. Tight public API; options/hooks/struct tags for extension.
5. Ship small, ship often. One change per commit. One concern per PR. Tag and release frequently.

How I write Go