"Uncle" Bob Martin

> it's both easier and more profitable to tell people that they need to OOP better than to use more appropriate paradigms in the design of their code. I don't think this is quite on target. Sure, he needs to go where the people are in order to communicate to the most people, but that doesn't mean he doesn't speak out against fads if it's appropriate. This talk was really formative for me: link If I remember correctly, he rails against just sticking the database in the middle of your system and calling that your architecture. If I'm remembering ▶ this video correctly, he says OOP is no big deal, it's just encapsulation-polymorphism-inheritance, and then goes on to say things like C had better encapsulation than OO languages (you can keep your .c file to yourself, and just give someone the .h to program against.). And c-style bytes with stdin/stdout was designed with perfect forward-compatibility - programs like your terminal don't need to be recompiled even though they interact with your program (which was written after). And for the last 5+ years he's been pushing FP pretty hard, especially closure. I don't see him as pushing OO on people at the expense of anything else.

There's a good talk here from Uncle Bob who helped popularise the solid principles, about what OOP is, and isn't ▶ this video Towards the end of the talk note of the stickers on his laptop

To quote ironic remark from "Uncle" Bob Martin: > Why do we write the code that slows us down? > And the answer to that is "Well, because we had to go fast! ▶ this video