The writer makes some good points. OOP sometimes encourages a mindset that certain problems (maintainability, modularity, etc.) can be ignored simply because a developer is composing objects. But without proper design up-front and close attention paid to the quality of the code being written, refactoring can double when things go awry.

That being said, most of the complaints are related to undisciplined/unskilled developers for whom advanced OOP design is a minefield.

While the author makes several good points, I think he/she has been too heavily influenced by C++'s brand of OO to be making broad generalizations about the entire paradigm.