How I Write Go
I've been lucky enough to use Go across several companies since about 2015. I've found it to be a nice choice for highly technical projects, but also a good choice for "basic business" stuff.
For the past few years, I've found myself maintaining a very large surface area of these "basic business" type projects, often as a single developer. This means working on APIs, wep applications, integrations between other systems, and so forth, all for different business units. Often times a projet will be comepleted with a few weeks, work for months or years without anyone touching it, and then have new requirements come in.
It is in this context that the style and patterns I've come to enjoy using have evolved. I don't pretent that this is the "correct" way to do things - that's up for you to decide for youself on your own projects, but if you're looking for a starting point, or just looking for some examples, I hope this is helpful to you.