Dont Write Poo
http://www.codinghorror.com/blog/archives/000801.html
Jeff Atwood at CodingHorror strikes again... speaking the heretical truth that OOP isn't the second coming of Jesus. I mean, it's good and all, and most of the time, it works more than it doesn't. But it isn't panacea, and sometimes, it proves the axiom that slavish adherence to dogma almost never turns out well.
The key is to not throw the baby out with the bathwater. Only recently did OOP become something I cared to do in the C# world - as I have mentioned before (i.e. with generics, LINQ, Lambdas, and reasonable tools for data layer automation, OOP in C# isn't that bad). And thankfully, we have more innovation in programming languages in the last couple years hitting closer to the mainstream than we had in the last 10 - Python, Ruby, Lisp, Haskell, and many others are starting to at least get mentioned more and more... not that I endorse those, but at least, it isn't the C#/Java/VB/PHP channel all the time.
That said, I would rather have someone on my team who could understand and solve business problems with code, than someone who could not, but could really build a kick-butt object model, all other things being equal. In other words, if you can write code that will, say, figure out the best set of product bundles in a purchasing scenario in an annual bidding process - and understand the complexities in that, frankly, I don't care what "programming church" you belong to.