Applied Go

POSIX threads have an array of control functions, goroutines have none. When to exit is a goroutine's decision. Here's how to properly stop them from the outside.

Anonymous types may seem like a suitable shortcut for simple scenarios, but the drawbacks don't outweigh the (perceived) benefits.

I would have called them modest pointers. They are unobtrusive and don't leave any garbage behind.

Define an anonymous function and invoke it right away: A pattern that is sometimes useful but hard to read and hence qualifies as 'clever, not clear'

You might feel powerless in the face of recent and upcoming disruptions. Think twice: Your Go skills are your secret weapon.

Go doesn't enforce struct initialization to be complete. A linter helps to catch half-baked initialization.

Go CLI tools should come with a man page. Here is how to distribute a man page with Goreleaser and homebrew

Go has an unconventional way of specifing time format. While time format strings can be confusing to construct, they are dead easy to read.

In a diamond-shaped class hierarchy, methods can be ambiguous. Go has no class hierarchies, but struct embedding can cause a similar problem.

RTFM! But what if the CLI tool has no man page? Make your users happy by providing a manpage alongside your CLI app.