There's nothing really to this article, no offence to the writer. How did it get on to the front page of HN?
The gist of the article is: "code review is cool, I did it this way, I got this. from my experience, here is the way it feels, and the cost of not doing it". It's shallow, but it's not empty. Just an enthousiastic experience sharing.
One thing that I find troubling is code review within FLOSS organisations and how Github doesn't let maintainers push to my PR. It's annoying to get your patch rejected because of a typo or lack of squashed commits, for example.
That's why we have contributing guidelines to follow :)
GitHub PRs only show you changes (unless you dig deeper) and not the grand scheme of things.