The author seems to equate OOP with “writing classes”. So I have to suggest that OOP never happened for them in the first place, at least not in the sense I un

The author seems to equate OOP with “writing classes”. So I have to suggest that OOP never happened for them in the first place, at least not in the sense I understand it viz. messaging, encapsulation, and late binding. The design discipline that falls out of this is, for me, domain modelling, not “writing classes”, and the value I’ve obtained being thereby a better fit between the structure of code, and the purpose of that code, with all the opportunities for validation and comprehension by domain experts that follows. That said, I do agree with the sentiment that multi-paradigm languages offer higher developer productivity than purist languages. I’d still have procedural style in fourth place, behind OO, FP, and Logic.