I find that the other approach is more likely to invent the kind of annoying and harmful revenue strategies you're criticizing. A product that has a built-in market of customers waving money does not need to stoop to that level to turn a profit. You can focus on making a product that your customers like and making sure they know about it.
How you prioritize making money is up to you. The OP is a helpful tip on getting it if you want it.
That's where the confusion is. That's not what the author intends. Basically what he's saying is that you can't just build something and expect to get paid for it. Switch out the word expect for "demand" and that might help matters. Just because you create something doesn't mean people are obligated to pay for it. Expecting that is wrong.
The author doesn't believe in putting money above all else. You don't even need to monetize early. But you need to have a plan. Just expecting things to work out all right is the wrong way to do it.
I doubt we have that different of an outlook. My passionate disagreement with the original author however is the belief you have to put making money above all else. I've seen too many startups end in failure (many of them clients) because they tried to monetize too early, or put nickle and diming customers above user satisfaction.