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

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

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

No, this one isn't obvious. And it's probably not having the impact you think it has. But it's still worth knowing.

'We ported this app to Go and see a 200% performance increase!' Just by porting the app line by line to Go? Probably not.

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

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.

A proposed new syntax for error checking promises clearer code, but the syntax may lead to carelessly letting context-free errors bubble up the chain.