Nah, I've been around long enough to know that local simplicity ruled the day just as much if not more in pre-OOP days. OOP is great because it allows programm

Nah, I've been around long enough to know that local simplicity ruled the day just as much if not more in pre-OOP days. OOP is great because it allows programmers and architects to create reliable and clearly defined types as data building blocks. But sometimes the hard parts of the problem are not in the structure of runtime data. Classic imperative and structured programming focused on the format of input data as the driver for code architecture, and that is the right way to design processes. Performance-oriented code needs to pay attention to data access more than to data structure or even to operations. Doing only OOP takes your attention away from those issues, and thus limits your design. Also, OOP focuses your attention on abstraction, and with a large enough problem, lack of visibility and clarity of requirements lead you to abstraction for abstraction's sake.