What a Go codebase needs beyond correct functions: packages and modules and the layout arguments worth ignoring, table-driven tests and the tooling that makes Go's testing unusually good, benchmarks and profiles that measure rather than guess, the parts of the standard library that repay study, and command-line programs with configuration that survives contact with operations.
No reviews yet.