> I'm not sure what the title has to do with the article at all.

The title has to do with a common use case of Go, referred to in the opening example, where it is a common choice to move to from Python for speed.

> It's just pointing out a language gotcha/subtlety.

The implied motivation for posting this (see the closing line) is that the author has see this bite people coming to Go from Python.