The trend of "all OOP" especially in the Java world, and how OOP is done, is BAD. As in "there's something in my eye" bad.This reflects exactly on this: "Reviews preferred local simplicity over global simplicity; abstraction was discouraged"
I feel like I'm a million years old, but I think procedural programming does it right.
It seems most OOP programmers want an excuse to do 10 levels of inheritance and split the functionality in weird ways.
The rest seems likely to derive from google's broken hiring process.
The trend of "all OOP" especially in the Java world, and how OOP is done, is BAD. As in "there's something in my eye" bad.This reflects exactly on this: "Reviews preferred local simplicity over global simplicity; abstraction was discouraged"
I feel like I'm a million years old, but I think procedural programming does it right.
It seems most OOP programmers want an excuse to do 10 levels of inheritance and split the functionality in weird ways.
The rest seems likely to derive from google's broken hiring process.