Author here. I linked to your post and there are comments on the blog (which you took advantage of). No need to be pissed off. I still disagree with this particular point (and I'm not sure why you say I took that quote out of context), despite your clarification. But overall I think you provide a lot of good and valuable advice that might be counterintuitive to younger devs entering the corporate world.
Thanks for the detailed feedback. I agree with a lot of your points, but I don't think adding QA people addresses the same need as peer code review. QA can find bugs in the current code whereas code review is more about finding issues that may lead to bugs further down the road. Even when there are defects in the current code, they may be edge cases that QA is unlikely to unearth but that will come out in a thorough code review.
Fair point about setup costs, but the marginal cost (which is what really counts over the long term) is negligeable in both cases.
Things are improving as I say in the piece, but it's worth noting that here in the Czech Republic I still have to pay nearly $200 for a month of data roaming in the US with a 200Mb cap. And that's if I go to the trouble of signing up for a special roaming plan, otherwise I could easily spent 10x that.
You're right, I should have made it more explicit that I run a software contracting company (though it's not exactly hidden either). In my defense I did mention the timezone difference, and I agree that it is perhaps the biggest issue. But I stand by my thesis: it's far better to work with great remote developers, despite the drawbacks, than mediocre local developers.