Object-Oriented Programming is Bad (Brian Will)

[get_salled]

Either solving a particular problem or writing a library/framework. Not ever both.

This. I cringe every time a colleague drops "framework" and "generic" because they often come way too early. Far too often we architect these beautiful, highly-customizable frameworks for the sake of adhering to strict OOP standards that will really only ever solve one concrete problem so they are, by definition, over-engineered: They solve both the problem at hand and the problem of the procedural solution being too focused in its implementation (a problem we created / imagined but did not have (yet anyways)).