Multiple return values and constant nil checking and error handling is odd - there are far better patterns for handling this but Go chose something that looks easy but doesn't scale well. I have other issues but writing good Go code that is easy to read feels very difficult.

Very short function parameters seems to be idiomatic but very odd as well. I never understood the desire to condense meaning as much as possible versus a more legible approach.