Just write a benchmark Fri, Sep 20, 2019 This is the 5th in a series of posts about Bad Go - a clickbaity title for posts about Go code that I’ve found frustrating because it could just be that little bit better. Better in my mind means more performant with less impact on GC, without being more complex or harder to read. In this post I’ll rant about a problem I’ve seen in a number of blog posts. I