I literally wrote an entire book on this syndrome
Back in 1995 -- after shipping a desktop publishing system built using Objective-C, for Nextstep -- I published a book titled "Pitfalls of Object-Oriented Development" (M&T Books, 1995). The first few chapters were pretty much about this tendency. Here are a just a few of the many pitfalls discussed:
Pitfall 1.1: Going object-oriented for the wrong reasons.
Pitfall 1.2: Thinking objects come for free.
Pitfall 1.3: Thinking objects will solve all problems.
Pitfall 1.4: Thinking that object technology is mature.
Pitfall 2.1: Not educating and enlisting management before the fact.
Pitfall 2.2: Underestimating the resistance.
Pitfall 2.3: Overselling the technology.
Pitfall 2.4: Getting religious about object-oriented development.
Pitfall 2.5: Not recognizing the politics of architecture.
Pitfall 2.6: Getting on the feature-release treadmill.
Pitfall 2.7: Betting the company on objects.
Pitfall 3.1: Adopting objects without well-defined objectives.
Pitfall 3.2: Cramming objects down the developers’ throats.
Pitfall 3.3: Abandoning good software engineering practices.
Pitfall 3.4: Not defining and using an effective methodology.
Pitfall 3.5: Attempting too much, too soon, too fast.
And so on, and so forth. What I have since discovered, as per the article above, is that this applies to any new technology or methodology. Some things never change. ..bruce..