If an assumption can be made that you won't put null values into the map then it can be rewritten where it doesn't need to do the check described above:
value = map.get(key);
if (null == value) {
// Handle no value in the map
}
I think one of the points of the OP's article is that in Go you don't have to code like you've done here, where a single return value means one of two things (in your example: value in the map, or special reserved value that indicates the key wasn't found in the map). Go is cleaner, even if it's just a small improvement.