Despite the hype, OO isn't a panacea. It's entirely possible to create lousy designs using OO, and unfortunately, it sounds like that might be the situation you're running into.

When I was first exposed to OO principles, I found that many of the touted OO advantages had analogs in things I considered plain old good software engineering practice from my straight-C days: using libraries to avoid re-inventing the wheel (code re-use), "private" structure definitions (data encapsulation), well-defined accessor APIs (method calls). OO does go beyond that, though, making it easy to do nifty things like inheritance that are, at best, laborious without an OO language.

Learning OO has actually made me a more effective non-OO programmer, too, so don't let a first sour taste turn you off. There's plenty of value in learning the principles, if only to give your mental toolbox an alternate way of approaching programming problems.