Applied Go

Containers manage binaries and their supporting libs. Pure Go binaries don't need any external libs. Is the `scratch` image the right choice?

A Go binary contains intersting details about the build process, such as Go version, dependencies, or build flags.

Can multiple goroutines write to the same slice without any safeguard? Sure, they can, but is it a good idea?

In a select block, don't be tempted to add a default case as a "fallback" or it might turn into a busy loop.

Go has no native sum types. Does Go need them at all, given that it has multi-value returns, and is it possible to implement a custom sum type?

At first sight, dot imports seem to make code clearer. However, in the end they only create more confusion than clarity.