How I Write Go
I've been lucky enough to use Go across several companies since about 2015. I think it's a great language for 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 small projects will be completed with a week or so, work for months or years without anyone touching them, and then have new requirements come in that need to be quickly implemented without breaking anything.
It is in this context that the style and patterns I've come to enjoy using have evolved. I don't pretend that this is the "correct" way to do things - that's up for you to decide for yourself 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.