Applied Go

Security is more crucial than ever. Making security an afterthought is a footgun. Learn how to write secure Go code from the start.

After a long (and exciting) journey through umpteenth of programming languages, I arrived at Go and finally feel at home.

Programming language theory doesn't rule out import cycles ... but this doesn't make them a good idea.

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

This happens when JSON and CSV have a baby. (And how your Go code can benefit from it.)

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

Clipping a slice doesn't free any memory. What is slices.Clip() good for then?

Are option types a good idea, or are they just syntactic sugar?

Debuggers tend to go overboard with features and subcommands. This Delve cheatsheet lists the most important commands that cover 90% of all use cases.

Is a slice of values faster than a slice of pointers? Does it even matter?