Applied Go

'Minimize dependencies, use the standard library!' is a well-known advice.

Start small, stay small: the core of a minimalist SaaS platform

Go has a small language specification, but does this make it a language for minimalist development?

Language criticism can be useful if it doesn't decline into mere nitpicking for the sake of it.

LLMs can just chat, unless you give them tools for working with files, searching the web, or... determining the current phase of the moon.

Fighting cross-site request forgery (CSRF) becomes easier in Go 1.25, thanks to the new cross origin protection feature.

Go's templates allow defining custom functions for use inside the template. Nice, but type safety gets overboard. Are they still worth using?

Letting an LLM code some tool in Go can be nice, especially when it uses tools via MCP. But there are some risks involved.

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

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