The following is a list of practical advice that will help you to write better Go code:
- If you have an error in a Go function, either log it or return it; do not do both unless you have a really good reason for doing so.
- Go interfaces define behaviors not data and data structures.
- Use the io.Reader and io.Writer interfaces when possible because they make your code more extensible.
- Make sure that you pass a pointer to a variable to a function only when needed. The rest of the time, just pass the value of the variable.
- Error variables are not string variables; they are error variables!
- Do not test your Go code on production machines unless you have a really good reason to do so.
- If you do not really know a Go feature, test it before using it for the first time, especially if you are developing an application or a utility that will be used by a large number...
