Applied Go

Generate Go code from an OpenAPI spec, or vice versa? You decide. These tools help you go both ways.

What's better than learning by inspecting real code? These repositories can help you transition from 'I know Go' to 'I understand how to use Go'.

Passing values through channels is fine, but beware of passing (hidden) pointers between goroutines.

The go.work file manages local redirects of remote modules. It's specific to your machine, so don't add it to the repository.

Or: don't hard-code your demo server port to 8080. Let it choose the next available port instead.

Instead of accessing your local dev servers through different port numbers, use Caddy to access them through separate domains.

Don't do this or you must go to bed without committing your code.

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

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