A comprehensive bit of guidance on writing effective Go.
I think Dave Cheney might have presented this blog post as a talk or a session at a QConference in China, but it's been posted on his blog and I refer back to it regularly. I originally found it in the "Further Reading" section of Alex Edwards' excellent Let's Go course, which I recommend to anyone wanting to learn Go.
The post is a bit of a read, but I've found it's nice to come back to in sessions. Helps orient me when I try to figure out what makes good code.