Here’s the reference material I use to help guide me on basic style, design, and general idiomatic Go practices.
|Go Style Guide||A guide to writing Go code.|
|Uber Go Styleguide||A thorough stylistic guide (opinionated, but great explanations on why)|
|Practical Go - Dave Cheney||A great practical guide from a well-respected authority in the Go community|
Principles I’ve gleaned over time and am quoting or bookmarking.
Source: Bill Kennedy in Ultimate Go [^readability]
If we are doing construction on a variable, we use value construction. Avoid pointer semantic construction if it’s not being returned.
Making the cost obvious and visible is a high priority for creating readable, maintainable code in a team context.