I second the recommendation Effective Go. It's a fairly quick read and routed me around a lot of poor design decisions: https://golang.org/doc/effective_go.htm

I second the recommendation Effective Go. It's a fairly quick read and routed me around a lot of poor design decisions: https://golang.org/doc/effective_go.html https://golang.org/doc/effective_go.html