I feel like the err != nil issue combines with GO using initialization to 0 values to be annoying. If you forget err != nil, well your value does actually have

I feel like the err != nil issue combines with GO using initialization to 0 values to be annoying. If you forget err != nil, well your value does actually have a value and you would think your result was 0.