You are correct. OO is too complex for the enterprise, because the requirements are simple and the deadlines are short. If you use complex OO hierarchies, you

You are correct. OO is too complex for the enterprise, because the requirements are simple and the deadlines are short. If you use complex OO hierarchies, you are going to over-engineer the solution, because it really does not require all that OO flexibility. You will also make things impossible to debug or maintain, and blow your deadlines. You need just enough OO to implement common patterns, but if I see more than that, I assume the programmer is new to real-world enterprise software development. Most enterprise software is just glue, and it is not spelled 'glOO'.