Applied Go

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?

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.